https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102906
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |testsuite
--- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
> then size ivopts-4.o:
> text data bss dec hex filename
> 38 0 0 38 26 ivopts-4.o
> where the testcase expects text <= 36
Ohhhhh, this is an object size regression? This test seems very fragile. Jump
threading will alter code size, so any change in the threading rules will
likely have an effect on code size. I suggest you add -fno-thread-jumps to the
test and adjust the object-size test accordingly.
This is a testsuite regression that must be fixed by the target maintainers,
not a middle-end or tree-optimization regression. I've marked it as so.
>
> My GCC is configured with --with-float=hard --with-cpu=cortex-a9
> --with-fpu=neon --with-mode=arm
>
> >
> > And just to be clear, it would be easier if someone could reproduce with a
> > cc1 / gcc command line, and not by pointing us to some table in a web page.
>
> Sorry, these automated validations builds are deleted after the reports are
> generated,
> so it's not really easier for me to manually reproduce than for anyone else.
That's why it's better to include actual command lines, and not web pages that
may change after the PR has been created.
