public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10213: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC Date: Mon, 19 May 2003 13:56:00 -0000 [thread overview] Message-ID: <20030519135602.13425.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10213; it has been noted by GNATS. From: Jan Hubicka <jh@suse.cz> To: snyder <snyder@fnal.gov> Cc: Jan Hubicka <jh@suse.cz>, bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: target/10213: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC Date: Mon, 19 May 2003 15:51:43 +0200 > > hi - > > >Jan Hubicka writes: > >Can you point me to the patch? I was off for a while and missed the > >thread. In case the fast prologues was disabled, I would like to fix > >the real problem instead. > > I think this is the patch that i was remembering: > > Thu Apr 3 00:18:49 CEST 2003 Jan Hubicka <jh@suse.cz> > > * i386.c (override_options): Disable red zone by default on i386. > (compute_frame_layout, ix86_force_to_memory, ix86_free_from_memory): > Do not test TARGET_64BIT together with TARGET_RED_ZONE > > > I admit i never looked at the actual code, though, to be sure > of what it was doing. When i saw that appear in the changelog, > i thought that it was a reaction to the bug that i had reported... I see, that patch disable red zone on i386, where one can't use it but not for x86-64, so the code path is not dead. The bugreport is ineed solved and can be closed. Thanks! Honza > > sss
next reply other threads:[~2003-05-19 13:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 13:56 Jan Hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-19 13:54 bangerth 2003-05-19 4:36 snyder 2003-05-18 18:46 Jan Hubicka 2003-05-15 4:41 bangerth 2003-05-15 1:06 snyder 2003-05-15 0:36 Dara Hazeghi 2003-03-26 8:31 steven
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=20030519135602.13425.qmail@sources.redhat.com \ --to=jh@suse.cz \ --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).