public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maciej at opencsw dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/61303] gccgo: segfault, regression since 4.8.2 Date: Sun, 03 May 2015 21:02:00 -0000 [thread overview] Message-ID: <bug-61303-4-7BtfHTQQW3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61303 --- Comment #7 from Maciej Bliziński <maciej at opencsw dot org> --- Checked again, the problem is still there in GCC-5.1. >From gcc-bugs-return-485310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 03 21:06:10 2015 Return-Path: <gcc-bugs-return-485310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28178 invoked by alias); 3 May 2015 21:06:10 -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 28116 invoked by uid 55); 3 May 2015 21:06:04 -0000 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: Sun, 03 May 2015 21:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: LpSolit at netscape dot net X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: LpSolit at netscape dot net X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-64968-4-5BTgJSlgeX@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-64968-4@http.gcc.gnu.org/bugzilla/> References: <bug-64968-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/msg00150.txt.bz2 Content-length: 1034 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64968 --- Comment #34 from Frédéric Buclin <LpSolit at netscape dot net> --- My debug code caught the problem. In one of the last bugmails, I got: Date: Sun, 03 May 2015 14:56:33 +0000 X-Bugzilla-Debug-Date: Sun, 03 May 2015 14:56:33 +0000 X-Bugzilla-Debug-DeltaTS: 2015-05-03 20:26:33 X-Bugzilla-Debug-Local_Timezone: Asia/Kolkata X-Bugzilla-TZ-FromEnv: Asia/Kolkata X-Bugzilla-TZ-FromEtcTimezone: no data X-Bugzilla-TZ-FromEtcLocaltime: UTC X-Bugzilla-TZ-FromEtcTIMEZONE: no data X-Bugzilla-TZ-FromEtcSysconfigClock: UTC X-Bugzilla-TZ-FromEtcDefaultInit: no data DeltaTS contains the date stored in the DB; this one is correct. But while 98% of bugmails have "X-Bugzilla-TZ-FromEnv: no data", this one has "Asia/Kolkata". This header is populated by $ENV{TZ}. As it takes precedence over "FromEtcLocaltime: UTC", this explains why the timestamp is wrong. Now, I cannot explain why $ENV{TZ} = "Asia/Kolkata" from time to time. But at least, we know where to look at. >From gcc-bugs-return-485311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 03 21:32:46 2015 Return-Path: <gcc-bugs-return-485311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 47566 invoked by alias); 3 May 2015 21:32:46 -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 47526 invoked by uid 48); 3 May 2015 21:32:43 -0000 From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/48890] length of a character derived-type component with PARAMETER Date: Sun, 03 May 2015 21:32: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: 4.6.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: fxcoudert at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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: cc Message-ID: <bug-48890-4-Pd6zHhxFzu@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-48890-4@http.gcc.gnu.org/bugzilla/> References: <bug-48890-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/msg00151.txt.bz2 Content-length: 871 https://gcc.gnu.org/bugzilla/show_bug.cgi?idH890 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu.org --- Comment #2 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- This is indeed a wrong-code bug. It's been reported on comp.lang.fortran today: implicit none type :: a_t character(len\x10) :: s = "x" end type a_t type(a_t), parameter :: foo = a_t("") type(a_t), parameter :: bar = a_t() print *, len(foo%s), len_trim(foo%s) print *, len(bar%s), len_trim(bar%s) end gives 0 0 10 1 while it should give: 10 0 10 1
next prev parent reply other threads:[~2015-05-03 21:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-24 14:16 [Bug go/61303] New: " maciej at opencsw dot org 2014-05-24 15:23 ` [Bug go/61303] " maciej at opencsw dot org 2014-07-20 12:33 ` maciej at opencsw dot org 2014-07-20 15:18 ` ian at airs dot com 2014-08-09 15:04 ` maciej at opencsw dot org 2015-05-03 21:02 ` maciej at opencsw dot org [this message] 2015-05-04 12:35 ` maciej at opencsw dot org 2015-05-08 23:27 ` ian at airs dot com
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-61303-4-7BtfHTQQW3@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).