public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/61886] [4.8/4.9/5 Regression] LTO breaks fread with _FORTIFY_SOURCE=2 Date: Mon, 06 Oct 2014 22:19:00 -0000 [thread overview] Message-ID: <bug-61886-4-TFFmrbsg7B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61886-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61886 --- Comment #15 from Jan Hubicka <hubicka at ucw dot cz> --- > On Mon, Oct 06, 2014 at 11:55:23PM +0200, Jan Hubicka wrote: > > Hi, > > I am testing this variant of the patch. > > For gcc-4.9 branch it may make sense to enable the new patch for LTO only. > > Not printing the inlining backtrace would be IMHO a significant regression. OK, how do I print it? I keep the BLOCK of the original expresison, so it is there. Honza > > Jakub >From gcc-bugs-return-463410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 06 22:27:38 2014 Return-Path: <gcc-bugs-return-463410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 5182 invoked by alias); 6 Oct 2014 22:27:38 -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 5157 invoked by uid 48); 6 Oct 2014 22:27:34 -0000 From: "davidgkinniburgh at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/63469] New: Automatic reallocation of allocatable scalar length even when substring implicitly specified Date: Mon, 06 Oct 2014 22:27:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: davidgkinniburgh at yahoo dot co.uk X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-63469-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: 2014-10/txt/msg00431.txt.bz2 Content-length: 1323 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc469 Bug ID: 63469 Summary: Automatic reallocation of allocatable scalar length even when substring implicitly specified Product: gcc Version: 4.9.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: davidgkinniburgh at yahoo dot co.uk CHARACTER(:), ALLOCATABLE :: s ALLOCATE (character(32) :: s) s(1:32) = 'string' print *, 'Length of ', s, ' with substring = ', LEN(s) s(:) = 'string' print *, 'Length of ', s, ' with substring = ', LEN(s) s = 'string' print *, 'Length of ', s, ' without substring = ', LEN(s) gfortran (4.9.1 and earlier) gives: Length of string with substring = 32 Length of string with substring = 6 Length of string without substring = 6 IVF (15.0) gives: Length of string with substring = 32 Length of string with substring = 32 Length of string without substring = 6 which I think is correct. It is the implicit definition of both the beginning and the ending of 's' that seems to do the damage.
next prev parent reply other threads:[~2014-10-06 22:19 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-61886-4@http.gcc.gnu.org/bugzilla/> 2014-07-23 10:58 ` [Bug lto/61886] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-07-23 11:13 ` rguenth at gcc dot gnu.org 2014-07-23 13:08 ` rguenth at gcc dot gnu.org 2014-07-23 13:37 ` hubicka at gcc dot gnu.org 2014-08-27 10:00 ` [Bug lto/61886] [4.8/4.9/5 " rguenth at gcc dot gnu.org 2014-08-27 14:51 ` hubicka at ucw dot cz 2014-08-28 8:20 ` rguenther at suse dot de 2014-09-08 0:42 ` hubicka at ucw dot cz 2014-09-08 7:53 ` rguenther at suse dot de 2014-10-06 20:23 ` hubicka at ucw dot cz 2014-10-06 20:34 ` jakub at redhat dot com 2014-10-06 22:08 ` jakub at redhat dot com 2014-10-06 22:19 ` hubicka at ucw dot cz [this message] 2014-10-06 22:38 ` jakub at redhat dot com 2014-10-06 22:44 ` hubicka at ucw dot cz 2014-10-07 5:46 ` hubicka at ucw dot cz 2014-10-07 9:24 ` jakub at gcc dot gnu.org 2014-10-07 9:35 ` jakub at gcc dot gnu.org 2014-10-07 19:49 ` hubicka at ucw dot cz 2014-10-08 7:37 ` rguenther at suse dot de 2014-10-08 8:25 ` jakub at gcc dot gnu.org 2014-10-08 10:42 ` rguenther at suse dot de 2014-10-08 17:49 ` hubicka at ucw dot cz 2014-12-01 12:31 ` rguenth at gcc dot gnu.org 2014-12-19 13:37 ` jakub at gcc dot gnu.org 2015-01-19 13:16 ` rguenth at gcc dot gnu.org 2015-02-11 8:29 ` rguenth at gcc dot gnu.org 2015-02-11 8:33 ` rguenth at gcc dot gnu.org 2015-02-11 9:15 ` hubicka at ucw dot cz 2015-02-11 10:05 ` rguenther at suse dot de 2015-02-11 16:30 ` zackw at panix dot com 2015-03-03 19:12 ` hubicka at gcc dot gnu.org 2015-03-20 21:00 ` hubicka at gcc dot gnu.org 2015-06-23 8:21 ` [Bug lto/61886] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:10 ` [Bug lto/61886] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:35 ` 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-61886-4-TFFmrbsg7B@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).