tmp-lshift.s:106: Error: selected processor does not support ARM mode `vdup.32 d6,r3'

Jeffrey Walton noloader at gmail.com
Mon Dec 31 13:50:34 UTC 2018


On Mon, Dec 31, 2018 at 4:30 AM Torbjörn Granlund <tg at gmplib.org> wrote:
>
> Jeffrey Walton <noloader at gmail.com> writes:
>
>   No, I don't override the CFLAGS. I set them like:
>
>     CFLAGS="-g2 -O3 -DNDEBUG -march=native" ./configure ...
>
> You override set CFLAGS, you just set it?

No. Me overriding your flags is:

    ./configure ....
    make CFLAGS="..."

In this case I stomp on your flags.

>   What is wrong is obvious. The build is broken.
>
> What do you expect us to do?  Edit broken user supplied CFLAGS to work
> for every possible breakage?
>
> If you want your build to proceed, start without overriding CFLAGS.
> Does that work?  Great, work from there.

No, we cannot work from there. GMP selects screwed up release flags.
They are dangerous and insecure.

GMP is the only project I know that cannot handle simple release build
flags. And I build 66 of them here:
https://github.com/noloader/Build-Scripts .

GMP really should follow GNU Coding Standards. It is not that hard.

Jeff


More information about the gmp-bugs mailing list