public inbox for firstname.lastname@example.org help / color / mirror / Atom feed
From: Dara Hazeghi <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, Subject: Re: optimization/10774: Problem with ``-march=pentium4 -O'' Date: Thu, 15 May 2003 03: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: Dara Hazeghi <email@example.com> To: Mikhail Teterin <firstname.lastname@example.org> Cc: email@example.com Subject: Re: optimization/10774: Problem with ``-march=pentium4 -O'' Date: Wed, 14 May 2003 20:02:59 -0700 (PDT) > = By "works," you mean the testcase exhibits the > correct behavior? > = > = Dara > > Yes. I also tested the original problem I had -- > FreeBSD pow(3) was > producing incorrect results, when the libm was > compiled for P4, which, > for me, led to the failure of the lcms (see > littlecms.com) selftest. > After recompiling the libm with gcc33, I can get > through the lcms' > selftest. I wonder, if the fixes can be backported > to the 3.2.x branch, > so the OS vendors can incorporate them without > jumping to the 3.3 right > away... They can be backported. However, there is nobody maintaining the gcc 3.2 branch, so these fixes will probably be localized to the various distributors. Dara __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
next reply other threads:[~2003-05-15 3:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-15 3:06 Dara Hazeghi [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 1:06 Mikhail Teterin 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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).