public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50083] [4.7 regression] All 32-bit fortran tests fail on 32-bit Solaris
Date: Tue, 23 Aug 2011 18:21:00 -0000 [thread overview]
Message-ID: <bug-50083-4-aDorZlBeiJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50083-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50083
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
--- Comment #3 from Uros Bizjak <ubizjak at gmail dot com> 2011-08-23 18:16:49 UTC ---
(In reply to comment #2)
> Created attachment 25058 [details]
> Proposed patch to fallback to lround call
>
> I can't trigger the problem on Linux, can you please test attached patch - or
> eventually provide a testcase with all necessary compile flags.
Clock starts ticking ...
next prev parent reply other threads:[~2011-08-23 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 9:50 [Bug middle-end/50083] New: " ro at gcc dot gnu.org
2011-08-15 11:50 ` [Bug middle-end/50083] " rguenth at gcc dot gnu.org
2011-08-19 19:43 ` ubizjak at gmail dot com
2011-08-19 22:54 ` ubizjak at gmail dot com
2011-08-23 18:21 ` ubizjak at gmail dot com [this message]
2011-08-24 10:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-08-24 10:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-08-25 15:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-08-25 17:00 ` ubizjak at gmail dot com
2011-08-25 18:32 ` ubizjak at gmail dot com
2011-08-26 16:13 ` uros at gcc dot gnu.org
2011-08-26 16:14 ` ubizjak at gmail dot com
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=bug-50083-4-aDorZlBeiJ@http.gcc.gnu.org/bugzilla/ \
--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).