public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug web/64968] Upgrade GCC Bugzilla to 5.0 Date: Fri, 08 May 2015 18:55:00 -0000 [thread overview] Message-ID: <bug-64968-4-rQaaX248rN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64968-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64968 --- Comment #39 from Frédéric Buclin <LpSolit at netscape dot net> --- Bug fixed upstream, and here. :) >From gcc-bugs-return-485880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 08 18:58:50 2015 Return-Path: <gcc-bugs-return-485880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 9591 invoked by alias); 8 May 2015 18:58:50 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 9549 invoked by uid 48); 8 May 2015 18:58:47 -0000 From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65894] [6 Regression] severe regression in gfortran 6.0.0 Date: Fri, 08 May 2015 18:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: juergen.reuter at desy dot de X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-65894-4-0sFKies4tw@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-65894-4@http.gcc.gnu.org/bugzilla/> References: <bug-65894-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-05/txt/msg00720.txt.bz2 Content-length: 256 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65894 --- Comment #31 from Jürgen Reuter <juergen.reuter at desy dot de> --- Shall I do any checks now? It seems that Mikael's patch is doing the right thing, and you found the one that breaks it again. >From gcc-bugs-return-485881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 08 19:00:21 2015 Return-Path: <gcc-bugs-return-485881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 16680 invoked by alias); 8 May 2015 19:00:21 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 16072 invoked by uid 55); 8 May 2015 19:00:12 -0000 From: "mike.jost at hp dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66077] Right shift calculation error Date: Fri, 08 May 2015 19:00:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 4.4.7 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mike.jost at hp dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-66077-4-IcDqwbzmcT@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66077-4@http.gcc.gnu.org/bugzilla/> References: <bug-66077-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-05/txt/msg00721.txt.bz2 Content-length: 1469 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf077 --- Comment #2 from Mike Jost <mike.jost at hp dot com> --- Thanks for the explanation! Bit by the 64 bit. That will teach me to use uint32_t instead of assuming 32 for unsigned long. I've been running on 32 bit embedded targets for too long! Regards, Michael Jost mike.jost@hp.com Software Engineer Object Technology Solutions, Inc. (OTSI) contractor HP Roseville - R3U Q8 (916) 785-2815 -----Original Message----- From: pinskia at gcc dot gnu.org [mailto:gcc-bugzilla@gcc.gnu.org] Sent: Friday, May 08, 2015 11:40 AM To: Jost, Mike (OTSI Contractor) Subject: [Bug c/66077] Right shift calculation error https://gcc.gnu.org/bugzilla/show_bug.cgi?idf077 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Your X and Y are not correctly displaying. The correct values are: x = 0xF12B3740 y = 0x1F12B3740 You should be using %lX rather than %X to display unsigned long. Like: printf("x = 0x%lX\n", x); printf("y = 0x%lX\n", y); As you can see there is another bit set in the upper 32bits which causes the difference. -- You are receiving this mail because: You reported the bug.
next prev parent reply other threads:[~2015-05-08 18:55 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-07 14:23 [Bug web/64968] New: " LpSolit at netscape dot net 2015-02-07 14:44 ` [Bug web/64968] " trippels at gcc dot gnu.org 2015-02-09 10:39 ` LpSolit at netscape dot net 2015-02-09 11:43 ` fche at redhat dot com 2015-02-11 14:37 ` LpSolit at netscape dot net 2015-02-11 16:33 ` fche at redhat dot com 2015-02-11 20:46 ` LpSolit at netscape dot net 2015-02-11 20:48 ` LpSolit at netscape dot net 2015-04-18 18:30 ` LpSolit at netscape dot net 2015-04-27 15:13 ` mikael at gcc dot gnu.org 2015-04-27 17:39 ` fche at redhat dot com 2015-04-27 18:34 ` LpSolit at netscape dot net 2015-04-27 19:47 ` LpSolit at netscape dot net 2015-04-28 16:28 ` trippels at gcc dot gnu.org 2015-04-28 18:26 ` LpSolit at netscape dot net 2015-04-29 12:27 ` LpSolit at netscape dot net 2015-04-29 16:02 ` trippels at gcc dot gnu.org 2015-04-30 13:48 ` trippels at gcc dot gnu.org 2015-04-30 16:34 ` LpSolit at netscape dot net 2015-04-30 20:53 ` LpSolit at netscape dot net 2015-05-01 9:16 ` LpSolit at netscape dot net 2015-05-03 1:00 ` LpSolit at netscape dot net 2015-05-08 6:22 ` trippels at gcc dot gnu.org 2015-05-08 6:46 ` schwab@linux-m68k.org 2015-05-08 6:51 ` trippels at gcc dot gnu.org 2015-05-08 11:02 ` LpSolit at netscape dot net 2015-05-08 18:55 ` LpSolit at netscape dot net [this message] 2015-05-08 19:04 ` trippels at gcc dot gnu.org 2015-05-15 14:06 ` LpSolit at netscape dot net 2015-05-26 14:15 ` trippels at gcc dot gnu.org 2015-05-26 17:41 ` fche at redhat dot com 2015-07-13 10:49 ` trippels at gcc dot gnu.org 2015-09-25 9:05 ` trippels at gcc dot gnu.org 2015-09-26 15:28 ` LpSolit at netscape dot net
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-64968-4-rQaaX248rN@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).