public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/10901: non-local goto's (still) don't work on apple-powerpc-darwin Date: Wed, 21 May 2003 13:06:00 -0000 [thread overview] Message-ID: <20030521130600.30370.qmail@sources.redhat.com> (raw) The following reply was made to PR other/10901; it has been noted by GNATS. From: Andrew Pinski <pinskia@physics.uc.edu> To: gcc@microbizz.nl Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-gnats@gcc.gnu.org, "Gcc-Bugs@Gcc. Gnu. Org" <gcc-bugs@gcc.gnu.org> Subject: Re: other/10901: non-local goto's (still) don't work on apple-powerpc-darwin Date: Wed, 21 May 2003 08:58:21 -0400 This should be target, as it only effects powerpc-apple-darwin. In 3.4 (do not know about 3.3): It looks like the register that is holding the pic address is overwritten in bar so when the jump happens the pic register now holds the pic for bar, not for main so it prints out some garbage. It looks like it should save and restore it in r30 like stack register is. A workaround in 3.4 for applications is to use -mdynamic-no-pic which will get rid of the pic code. Thanks, Andrew Pinski On Wednesday, May 21, 2003, at 06:15 US/Eastern, gcc@microbizz.nl wrote: > extern int puts (const char *); > extern void abort (void); > > int main (void) > { > __label__ l1; > > void foo (void) > { > > void bar (void) > { > puts ("goto l1"); > goto l1; > } > > bar (); > } > > foo (); > abort (); > l1: > puts ("label l1"); > return 0; > } >> How-To-Repeat: > gcc nonlocalgoto.c -o nonlocalgoto -O3 > gcc nonlocalgoto.c -o nonlocalgoto -O0 > >> Fix: > >> Release-Note: >> Audit-Trail: >> Unformatted: > >
next reply other threads:[~2003-05-21 13:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-21 13:06 Andrew Pinski [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 10:33 gcc
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=20030521130600.30370.qmail@sources.redhat.com \ --to=pinskia@physics.uc.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).