public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50066] [4.7 Regression] Bad signed int to unsigned long long conversion
Date: Sat, 13 Aug 2011 20:03:00 -0000	[thread overview]
Message-ID: <bug-50066-4-pUOEbhAXZT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50066-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50066

--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-08-13 19:00:48 UTC ---
(In reply to comment #13)
> We should consider our users. GMP has been working with
> GCC for a long time. Now it fails with GCC 4.7. It is
> a very bad GCC 4.7 experience for user.

Yes and other packages failed when the original VPR and overflow was
introduced.  Why should this case be any different than all the others?


  parent reply	other threads:[~2011-08-13 19:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 23:46 [Bug middle-end/50066] New: [4.7 Regression] Bad signed long " hjl.tools at gmail dot com
2011-08-13  0:00 ` [Bug middle-end/50066] [4.7 Regression] Bad signed int " hjl.tools at gmail dot com
2011-08-13  7:05 ` pinskia at gcc dot gnu.org
2011-08-13 10:11 ` paolo.carlini at oracle dot com
2011-08-13 12:29 ` hjl.tools at gmail dot com
2011-08-13 14:54 ` hjl.tools at gmail dot com
2011-08-13 15:31 ` joseph at codesourcery dot com
2011-08-13 15:37 ` joseph at codesourcery dot com
2011-08-13 16:33 ` hjl.tools at gmail dot com
2011-08-13 17:04 ` hjl.tools at gmail dot com
2011-08-13 18:12 ` pinskia at gcc dot gnu.org
2011-08-13 18:17 ` hjl.tools at gmail dot com
2011-08-13 18:23 ` pinskia at gcc dot gnu.org
2011-08-13 18:33 ` hjl.tools at gmail dot com
2011-08-13 19:01 ` hjl.tools at gmail dot com
2011-08-13 20:03 ` pinskia at gcc dot gnu.org [this message]
2011-08-14  9:52 ` rguenth at gcc dot gnu.org
2011-11-30 21:19 ` hjl.tools at gmail dot com
2011-11-30 21:45 ` pinskia 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-50066-4-pUOEbhAXZT@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).