public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc at mrozekma dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56606] New: GCC refuses to emit long calls for operator new/delete on PowerPC Date: Tue, 12 Mar 2013 20:26:00 -0000 [thread overview] Message-ID: <bug-56606-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56606 Bug #: 56606 Summary: GCC refuses to emit long calls for operator new/delete on PowerPC Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: gcc@mrozekma.com -mlongcall seems to have no effect on operator new and operator delete. For example, given the code: > extern void foo(); > void bar() { > foo(); > new char; > } A normal run of GCC on PowerPC will generate the (abridged) assembly: > bl _Z3foov > bl _Znwj Running GCC with the -mlongcall option generates: > lis r9, _Z3foov@ha > addi r9, r9, _Z3foov@l > mtctr r9 > bctrl > bl _Znwj The branch to foo() was expanded as expected, but the branch to operator new is still short. Calls to random libc and libstdc++ functions are all converted; so far operator new and operator delete are the only ones I've seen that don't work. This seems similar to bug 12769, but that was for generated functions --- GCC build info: > Target: ppc-redhat-linux > Configured with: ./configure --prefix=/opt/gcc-4.7.2-ppc --mandir=/opt/gcc-4.7.2-ppc/share/man --enable-shared --enable-threads=posix --with-system-zlib --enable-languages=c,c++ --build=ppc-redhat-linux --host=ppc-redhat-linux --target=ppc-redhat-linux > gcc version 4.7.2 (GCC) Test compiled with: > g++ -mlongcall -c -o test.o test.cpp
next reply other threads:[~2013-03-12 20:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-12 20:26 gcc at mrozekma dot com [this message] 2013-03-14 20:20 ` [Bug c++/56606] " gcc at mrozekma dot com
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-56606-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).