[Bug target/65837] [arm-linux-gnueabihf] lto1 target specific builtin not available

ramana.radhakrishnan at arm dot com gcc-bugzilla@gcc.gnu.org
Thu Apr 23 11:29:00 GMT 2015


--- Comment #8 from ramana.radhakrishnan at arm dot com <ramana.radhakrishnan at arm dot com> ---
On 23/04/15 09:18, rguenth at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65837
> Richard Biener <rguenth at gcc dot gnu.org> changed:
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|RESOLVED                    |REOPENED
>     Last reconfirmed|                            |2015-04-23
>           Resolution|INVALID                     |---
>       Ever confirmed|0                           |1
> --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
> Not really - it's supported with GCC 5 that way as it uses target attributes.

The ARM backend doesn't support target attributes either as attributes 
to functions or as #pragmas. That's the real issue not that we don't 
initialize and stream the builtins in this corner case.

While doing that work we need to make sure we initialize the builtins 
for the appropriate options.

So the Chromium usecase is INVALID, I'd think.

But an additional PR to support target attributes in the ARM backend. 
There's a start with Christian Bruel's patches for arm and thumb but it 
needs extension to other options as well.


More information about the Gcc-bugs mailing list