public inbox for email@example.com help / color / mirror / Atom feed
From: Mikhail Teterin <Mikhail.Teterin@murex.com> To: firstname.lastname@example.org Cc: email@example.com, Subject: Re: optimization/10774: Problem with ``-march=pentium4 -O'' Date: Thu, 15 May 2003 01:06:00 -0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) The following reply was made to PR optimization/10774; it has been noted by GNATS. From: Mikhail Teterin <Mikhail.Teterin@murex.com> To: Dara Hazeghi <email@example.com>, das@FreeBSD.org, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Cc: obrien@FreeBSD.org Subject: Re: optimization/10774: Problem with ``-march=pentium4 -O'' Date: Wed, 14 May 2003 21:03:42 -0400 On Wednesday 14 May 2003 01:57 pm, Dara Hazeghi wrote: = http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10774 = = Hello, = = -march=pentium4 used to have problems. A good number were fixed in = gcc 3.3. Can you by any chance check that the problems still occur = when compiling with gcc 3.3 (I'd help, but don't have access to a = P-IV!)? Yes, the gcc version 3.3 20030509 (prerelease) [FreeBSD] and, presumably, the just released (3 hours after I finished building the prerelease) gcc-3.3 works too. I hope, FreeBSD updates its compiler the soonest -- prior to the 5.1 release... Thanks! -mi
next reply other threads:[~2003-05-15 1:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-15 1:06 Mikhail Teterin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-15 14:26 Mikhail Teterin 2003-05-15 13:55 bangerth 2003-05-15 3:06 Dara Hazeghi 2003-05-14 18:06 Dara Hazeghi 2003-05-14 0:26 mi+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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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).