public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Ronald Wahl <Ronald.Wahl@informatik.tu-chemnitz.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/9711: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer) Date: Sat, 15 Feb 2003 21:46:00 -0000 [thread overview] Message-ID: <20030215214601.16325.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/9711; it has been noted by GNATS. From: Ronald Wahl <Ronald.Wahl@informatik.tu-chemnitz.de> To: bangerth@dealii.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/9711: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer) Date: Sat, 15 Feb 2003 22:36:38 +0100 On 14 Feb 2003 22:15:53 -0000, bangerth wrote: > Synopsis: glibc 2.3.1 miscompiled (mcpu=i686, mcpu=athlon, -fomit-frame-pointer) > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Fri Feb 14 22:15:53 2003 > State-Changed-Why: > We need more information to tackle this problem. Please > review > http://gcc.gnu.org/bugs.html > for what we need and provide this information. > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9711 Maybe we can forget all about my bug report if one could tell me if it should matter if I specify march/mcpu options in cc1_options instead of cc1_cpu in the spec file. If this really matters then it should be documented somewhere I think. I had these options appended to cc1_options. If I move'em to cc1_cpu the problems go away. The -fomit-frame-pointer issue was already reported and there is an patch floating around. (http://gcc.gnu.org/ml/gcc/2002-07/msg00367.html) which I haven't tried yet. regards, ron
next reply other threads:[~2003-02-15 21:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-15 21:46 Ronald Wahl [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 23:06 Dara Hazeghi 2003-02-17 22:06 Wolfgang Bangerth 2003-02-17 18:36 Ronald Wahl 2003-02-17 17:16 Wolfgang Bangerth 2003-02-14 22:15 bangerth 2003-02-14 22:06 rwahl
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=20030215214601.16325.qmail@sources.redhat.com \ --to=ronald.wahl@informatik.tu-chemnitz.de \ --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).