public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47822] [4.6 Regression] Multiple test suite failures due to revision 170321 Date: Sun, 20 Feb 2011 15:14:00 -0000 [thread overview] Message-ID: <bug-47822-4-PeRogVszT8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47822-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47822 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-02-20 15:05:00 UTC --- Huh. WTF is this builtin used for at all?? int main() { return __builtin___CFStringMakeConstantString ("Hello"); } and at gimple stage we already have main () { int D.2718; long int D.2719; D.2719 = (long int) &C.1605; D.2718 = (int) D.2719; return D.2718; } !? It appearantly relies on folding, huh, another brokeness - there is no way it would survive through expansion (well, it'll get a libcall ...). I wonder where it is actually _used_ from!? Not from any header I have installed on x86_64-darwin, not from any GCC code either. Feels like a darwin hack again ... don't feel like wasting my Sunday on this one either.
next prev parent reply other threads:[~2011-02-20 15:05 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-20 11:13 [Bug lto/47822] New: " dominiq at lps dot ens.fr 2011-02-20 14:54 ` [Bug target/47822] " rguenth at gcc dot gnu.org 2011-02-20 15:14 ` rguenth at gcc dot gnu.org [this message] 2011-02-20 15:21 ` dominiq at lps dot ens.fr 2011-02-20 15:49 ` rguenth at gcc dot gnu.org 2011-02-20 16:24 ` dominiq at lps dot ens.fr 2011-02-20 17:23 ` rguenth at gcc dot gnu.org 2011-02-20 17:28 ` rguenth at gcc dot gnu.org 2011-02-20 18:49 ` mrs at gcc dot gnu.org 2011-02-20 19:03 ` mrs at gcc dot gnu.org 2011-02-20 19:35 ` dominiq at lps dot ens.fr 2011-02-20 19:40 ` mikestump at comcast dot net 2011-02-20 19:54 ` dominiq at lps dot ens.fr 2011-02-20 20:40 ` howarth at nitro dot med.uc.edu 2011-02-21 5:14 ` mrs at gcc dot gnu.org 2011-02-21 9:45 ` rguenth at gcc dot gnu.org 2011-02-21 10:09 ` dominiq at lps dot ens.fr 2011-02-21 10:37 ` iains at gcc dot gnu.org 2011-02-21 11:19 ` rguenth at gcc dot gnu.org 2011-02-21 21:34 ` mikestump at comcast dot net 2011-02-21 21:38 ` mikestump at comcast dot net 2011-02-21 21:48 ` mrs at gcc dot gnu.org 2011-02-22 10:52 ` dominiq at lps dot ens.fr 2011-02-22 12:01 ` mikestump at comcast dot net 2011-02-22 12:37 ` mikestump at comcast dot net
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-47822-4-PeRogVszT8@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: linkBe 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).