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 middle-end/50708] Infinite loop between rshift_double and lshift_double if count is LONG_MIN Date: Thu, 29 Mar 2012 08:29:00 -0000 [thread overview] Message-ID: <bug-50708-4-lbl212bWVC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50708-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50708 --- Comment #8 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-29 08:27:16 UTC --- Author: rguenth Date: Thu Mar 29 08:27:04 2012 New Revision: 185951 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=185951 Log: 2012-03-29 Richard Guenther <rguenther@suse.de> PR middle-end/50708 * double-int.h (rshift_double): Remove. * double-int.c (lshift_double): Use absu_hwi to make count positive. (rshift_double): Make static, take unsigned count argument, remove handling of negative count argument. (double_int_rshift): Dispatch to lshift_double. Modified: trunk/gcc/ChangeLog trunk/gcc/double-int.c trunk/gcc/double-int.h
next prev parent reply other threads:[~2012-03-29 8:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-12 20:27 [Bug middle-end/50708] New: " rmansfield at qnx dot com 2011-10-13 9:27 ` [Bug middle-end/50708] " rguenth at gcc dot gnu.org 2011-10-29 1:16 ` rmansfield at qnx dot com 2011-10-29 13:30 ` mikpe at it dot uu.se 2011-10-29 14:29 ` rmansfield at qnx dot com 2011-10-30 20:35 ` mikpe at it dot uu.se 2012-03-28 14:26 ` rguenth at gcc dot gnu.org 2012-03-28 14:34 ` rguenth at gcc dot gnu.org 2012-03-29 8:29 ` rguenth at gcc dot gnu.org [this message] 2012-03-29 9:32 ` rguenth at gcc dot gnu.org 2012-07-05 14:55 ` rguenth at gcc dot gnu.org 2012-07-06 9:26 ` rguenth at gcc dot gnu.org 2012-07-06 9:27 ` 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-50708-4-lbl212bWVC@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: linkBe 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).