public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joey.ye at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59884] Unexpected warning pragma GCC target
Date: Mon, 20 Jan 2014 03:56:00 -0000 [thread overview]
Message-ID: <bug-59884-4-w4c5hxVzNh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59884-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59884
--- Comment #2 from Joey Ye <joey.ye at arm dot com> ---
(In reply to Andrew Pinski from comment #1)
> Comes from:
> if (p->target_binary != target_option_current_node)
> {
> (void) targetm.target_option.pragma_parse (NULL_TREE,
> p->target_binary);
> target_option_current_node = p->target_binary;
> }
>
>
> The front-end expects the target always to implement these target hooks it
> seems rather than the default.
>
> Really I think the arm back-end should implement them so that thumb2 code
> can be in the same source file as arm32 code and would help out LTO when
> people mix and match them.
It is a useful feature on ARM. I don't know why it isn't support now.
But this warning still need to be fixed as there are always some targets not
supportting this pragma.
next prev parent reply other threads:[~2014-01-20 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 3:07 [Bug c/59884] New: " joey.ye at arm dot com
2014-01-20 3:46 ` [Bug target/59884] " pinskia at gcc dot gnu.org
2014-01-20 3:56 ` joey.ye at arm dot com [this message]
2015-04-30 9:59 ` ramana at gcc dot gnu.org
2015-05-20 12:59 ` chrbr at gcc dot gnu.org
2015-06-22 8:22 ` chrbr at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-59884-4-w4c5hxVzNh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).