public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50802] [4.7 Regression] FAIL: gcc.c-torture/execute/arith-rand-ll.c execution at -O2 and -Os
Date: Mon, 07 Nov 2011 15:21:00 -0000 [thread overview]
Message-ID: <bug-50802-4-4t5gcz2dIu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50802-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50802
--- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-07 15:09:54 UTC ---
Weird. My cross configured with
/space/rguenther/src/svn/trunk/configure --enable-languages=c,c++,fortran
--disable-nls --target=hppa2.0w-hp-hpux11.11
does not reproduce this. I'm using ./cc1 -O2 on arith-rand-ll.c, and I'm
getting
arith-rand-ll.c: In function 'main':
arith-rand-ll.c:59:4: warning: incompatible implicit declaration of built-in
function 'abort' [enabled by default]
...
not sure if that's related.
>From your dump file:
x_118: [0, +INF] EQUIVALENCES: { x_5 D.2243_12 } (2 elements)
xx_56: VARYING
D.2297_58: [-32768, 32767]
xx_56 = (short int) x_118;
Folding statement: D.2297_58 = (int) xx_56;
Folded into: D.2297_58 = (int) x_118;
should be reproducible with
extern void abort (void);
long long unsigned int x = 1 << (sizeof (short int) * 8);
int main()
{
if (x >= 0)
{
short int xx = (short int)x;
if (xx != 0)
abort ();
}
return 0;
}
but that works for me ... does this fail for you? Looking at the above
it _appears_ that x is signed!? The reported value-range should be
x_5: VARYING
which it is indeed when compiling with my cross ...
Is, by any chance, the middle-end sizetype == long long unsigned int?
And for some weird reason those are mapped together?
next prev parent reply other threads:[~2011-11-07 15:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 23:14 [Bug middle-end/50802] New: " danglin at gcc dot gnu.org
2011-10-20 9:01 ` [Bug middle-end/50802] " rguenth at gcc dot gnu.org
2011-10-23 19:54 ` danglin at gcc dot gnu.org
2011-10-24 0:02 ` [Bug tree-optimization/50802] " danglin at gcc dot gnu.org
2011-10-27 11:21 ` rguenth at gcc dot gnu.org
2011-10-27 11:50 ` dave.anglin at bell dot net
2011-10-30 20:00 ` danglin at gcc dot gnu.org
2011-11-07 1:05 ` danglin at gcc dot gnu.org
2011-11-07 11:07 ` rguenth at gcc dot gnu.org
2011-11-07 12:49 ` dave.anglin at bell dot net
2011-11-07 14:46 ` dave.anglin at bell dot net
2011-11-07 14:47 ` dave.anglin at bell dot net
2011-11-07 15:21 ` rguenth at gcc dot gnu.org [this message]
2011-11-07 16:15 ` dave.anglin at bell dot net
2011-11-07 16:20 ` dave.anglin at bell dot net
2011-11-17 2:34 ` danglin at gcc dot gnu.org
2011-11-18 20:37 ` amylaar at gcc dot gnu.org
2011-11-18 22:16 ` amylaar at gcc dot gnu.org
2011-11-18 22:27 ` amylaar at gcc dot gnu.org
2011-11-18 22:48 ` amylaar at gcc dot gnu.org
2011-11-19 3:48 ` amylaar at gcc dot gnu.org
2011-11-21 15:53 ` dave.anglin at bell dot net
2011-12-01 14:27 ` amylaar at gcc dot gnu.org
2011-12-06 12:05 ` rguenth at gcc dot gnu.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=bug-50802-4-4t5gcz2dIu@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).