public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49866] New: [4.6 Regression] -mcmodel=large tail call fails to assemble Date: Wed, 27 Jul 2011 11:40:00 -0000 [thread overview] Message-ID: <bug-49866-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49866 Summary: [4.6 Regression] -mcmodel=large tail call fails to assemble Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: jakub@gcc.gnu.org CC: uros@gcc.gnu.org Target: x86_64-linux void fn (void *, int, int); int fn2 (void); void baz (int); static void foo (void *x, int y) { int i; for (i = 0; i < y; i++) fn (x, fn2 (), i); } void bar (int u, int v, int w, void *x) { baz (u); foo (x, w); baz (u); } gcc -O2 -mcmodel=large -c rh725516.c fails to assemble, we end up with jmp *$baz This got fixed on the trunk with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173797 but for the backport it would be certainly preferrable if we got a smaller and less riskier fix than that. In r166110 it was (likely incorrectly for large model, but at least it assembled) emitting jmp baz, I expect the change came with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166119
next reply other threads:[~2011-07-27 11:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-27 11:40 jakub at gcc dot gnu.org [this message] 2011-07-27 11:42 ` [Bug target/49866] " jakub at gcc dot gnu.org 2011-07-27 11:47 ` ubizjak at gmail dot com 2011-07-27 12:09 ` jakub at gcc dot gnu.org 2011-07-27 12:15 ` ubizjak at gmail dot com 2011-07-27 12:52 ` jakub at gcc dot gnu.org 2011-07-27 12:56 ` ubizjak at gmail dot com 2011-07-27 18:17 ` jakub at gcc dot gnu.org 2011-07-27 18:20 ` jakub at gcc dot gnu.org 2011-07-27 19:24 ` jakub 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-49866-4@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).