public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/49123] [4.6 Regression] FAIL: gcc.c-torture/execute/pr48973-[12].c
Date: Mon, 23 May 2011 14:17:00 -0000 [thread overview]
Message-ID: <bug-49123-4-VVblQgOJWM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49123-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49123
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.6.1 |---
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-23 13:36:00 UTC ---
(In reply to comment #4)
> A less intrusive variant of the patch might be suitable for backporting
> (it doesn't touch the NULL type argument path) and fixes the testcase for me.
>
> Index: gcc/tree.c
> ===================================================================
> --- gcc/tree.c (revision 174066)
> +++ gcc/tree.c (working copy)
> @@ -1034,9 +1034,9 @@ build_int_cst (tree type, HOST_WIDE_INT
> {
> /* Support legacy code. */
> if (!type)
> - type = integer_type_node;
> + return build_int_cst_wide (integer_type_node, low, low < 0 ? -1 : 0);
>
> - return build_int_cst_wide (type, low, low < 0 ? -1 : 0);
> + return double_int_to_tree (type, shwi_to_double_int (low));
> }
>
> /* Create an INT_CST node with a LOW value in TYPE. The value is sign
> extended
Alternatively you could call build_int_cst_type instead of build_int_cst in the
spot where FRE? calls it. Guess that would be even safer to backport.
next prev parent reply other threads:[~2011-05-23 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 13:29 [Bug lto/49123] New: " hjl.tools at gmail dot com
2011-05-23 13:34 ` [Bug lto/49123] " rguenth at gcc dot gnu.org
2011-05-23 13:44 ` rguenth at gcc dot gnu.org
2011-05-23 13:45 ` rguenth at gcc dot gnu.org
2011-05-23 13:46 ` jakub at gcc dot gnu.org
2011-05-23 13:52 ` rguenth at gcc dot gnu.org
2011-05-23 14:17 ` jakub at gcc dot gnu.org [this message]
2011-05-23 14:23 ` rguenth at gcc dot gnu.org
2011-05-23 15:20 ` hjl.tools at gmail dot com
2011-05-23 20:55 ` jakub at gcc dot gnu.org
2011-05-23 20:56 ` jakub at gcc dot gnu.org
2011-05-23 21:02 ` jakub 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-49123-4-VVblQgOJWM@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).