public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc dot glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/40757] gcc 4.4.0 miscompiles mpfr-2.4.1
Date: Thu, 16 Jul 2009 20:34:00 -0000 [thread overview]
Message-ID: <20090716203430.4844.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40757-16207@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from marc dot glisse at normalesup dot org 2009-07-16 20:34 -------
(In reply to comment #11)
> for this memset call, which looks correct to me. The st %g1, [%i0+%l5] line
> stores to %i0 a[n-1] and memset is called with memset (a, 0, (n + 0x3fffffffU)
> << 2); So, if this doesn't work (and you see the same), you hit a bug in
> Solaris memset implementation, which doesn't handle properly length with
> garbage in upper 32-bits, guess it could use brz,pn %o2, do_nothing or
> something similar, which is fine for 64-bit code, but certainly not for 32-bit
> code.
The sun4v implementation in opensolaris looks fine (but may not have been
backported to solaris 10). The following one on the other hand seems to use the
same brnz for 32 and 64 bit code:
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/sparc_hwcap1/common/gen/memset.s#88
It would be good to know which implementation is used...
--
marc dot glisse at normalesup dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marc dot glisse at
| |normalesup dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40757
next prev parent reply other threads:[~2009-07-16 20:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 0:36 [Bug c/40757] New: " zimmerma+gcc at loria dot fr
2009-07-15 2:02 ` [Bug c/40757] " zimmerma+gcc at loria dot fr
2009-07-15 6:27 ` ebotcazou at gcc dot gnu dot org
2009-07-15 9:55 ` rguenth at gcc dot gnu dot org
2009-07-15 13:15 ` mikpe at it dot uu dot se
2009-07-16 7:52 ` zimmerma+gcc at loria dot fr
2009-07-16 8:31 ` mikpe at it dot uu dot se
2009-07-16 10:19 ` david dot kirkby at onetel dot net
2009-07-16 10:24 ` david dot kirkby at onetel dot net
2009-07-16 10:31 ` jakub at gcc dot gnu dot org
2009-07-16 12:32 ` david dot kirkby at onetel dot net
2009-07-16 14:07 ` jakub at gcc dot gnu dot org
2009-07-16 20:34 ` marc dot glisse at normalesup dot org [this message]
2009-07-16 21:29 ` david dot kirkby at onetel dot net
2009-07-17 0:58 ` zimmerma+gcc at loria dot fr
2009-07-17 3:22 ` david dot kirkby at onetel dot net
2009-07-17 4:11 ` david dot kirkby at onetel dot net
2009-07-17 7:49 ` jakub at gcc dot gnu dot org
2009-07-17 11:19 ` david dot kirkby at onetel dot net
2009-07-17 15:51 ` marc dot glisse at normalesup dot org
2009-07-18 1:14 ` david dot kirkby at onetel dot net
2009-07-18 1:18 ` david dot kirkby at onetel dot net
2009-07-18 4:50 ` marc dot glisse at normalesup dot org
2009-07-18 14:36 ` david dot kirkby at onetel dot net
2009-07-18 14:44 ` david dot kirkby at onetel dot net
2009-07-18 19:33 ` david dot kirkby at onetel dot net
2009-10-01 8:34 ` [Bug target/40757] " david dot kirkby at onetel dot net
2009-10-04 11:01 ` ebotcazou at gcc dot gnu dot org
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=20090716203430.4844.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).