public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65136] [5 Regression] VRP inserts unnecessary constant copy in the loop
Date: Fri, 20 Feb 2015 18:20:00 -0000	[thread overview]
Message-ID: <bug-65136-4-j8A3Ld8twb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65136-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65136

--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Richard Biener from comment #3)
> After the patch the assembly difference between 4.9 and 5 is

Hm, I don't see the difference with -O2, 4.9.3 vs. 5.0:

--- pr65136_493.s       2015-02-20 18:50:30.939970811 +0100
+++ pr65136_5.s 2015-02-20 18:50:36.860907527 +0100
@@ -31,5 +31,5 @@
 .LCOLDE0:
        .text
 .LHOTE0:
-       .ident  "GCC: (GNU) 4.9.3 20150204 (prerelease) [gcc-4_9-branch
revision 220411]"
+       .ident  "GCC: (GNU) 5.0.0 20150220 (experimental) [trunk revision
220876]"
        .section        .note.GNU-stack,"",@progbits
>From gcc-bugs-return-477987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 20 18:06:04 2015
Return-Path: <gcc-bugs-return-477987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30274 invoked by alias); 20 Feb 2015 18:06:04 -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 30049 invoked by uid 48); 20 Feb 2015 18:06:00 -0000
From: "zbeekman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65144] New: Problems printing, reading and accessing substrings of ISO_10646 character variables
Date: Fri, 20 Feb 2015 18:48: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.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zbeekman at gmail dot com
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 attachments.created
Message-ID: <bug-65144-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-02/txt/msg02319.txt.bz2
Content-length: 1471

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65144

            Bug ID: 65144
           Summary: Problems printing, reading and accessing substrings of
                    ISO_10646 character variables
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zbeekman at gmail dot com

Created attachment 34820
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34820&action=edit
reproducer program

This bug may be related to 65125,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65125 I’m not sure.

Basically it seems that 3 things are happening:

 - Unicode strings aren’t being output correctly to to stdout, it seems only
the first few characters are output. This *could* be an issue related to what
gfortran thinks the encoding of the tty is. Further testing reveals that it
seems to output to a file opened with uff-8 encoding OK
 - Unicode substrings retain the correct kind as long as they are not
parameters (see 65141 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65141) BUT
the resulting representation seems to be that of DEFAULT character kind. (i.e.
the characters change when a substring expression is used, characters 2-4 in
str(2:4) are different than characters 2-4 in str). This happens even when
writing to a file opened with uff-8 encoding.
>From gcc-bugs-return-477988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 20 18:20:20 2015
Return-Path: <gcc-bugs-return-477988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6245 invoked by alias); 20 Feb 2015 18:20:20 -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 6196 invoked by uid 48); 20 Feb 2015 18:20:16 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65109] [5 Regression] r220674 causes FAIL: gcc.target/powerpc/ppc64-abi-1.c execution test
Date: Fri, 20 Feb 2015 18:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-65109-4-zZ36rIIItm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65109-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-02/txt/msg02320.txt.bz2
Content-length: 634

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide109

Jeffrey A. Law <law at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at redhat dot com

--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
Martin,

Does the test pass if the schedulers are turned off?  If so, turning off the
schedulers would be less invasive.  Still leaves us with a bit of a fragile
test, but it's been like this for ~12 years or so.  Revisiting it once every
dozen years isn't so bad.


  parent reply	other threads:[~2015-02-20 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  9:56 [Bug tree-optimization/65136] New: " izamyatin at gmail dot com
2015-02-20 12:43 ` [Bug tree-optimization/65136] [5 Regression] " rguenth at gcc dot gnu.org
2015-02-20 17:03 ` rguenth at gcc dot gnu.org
2015-02-20 17:05 ` rguenth at gcc dot gnu.org
2015-02-20 18:20 ` ubizjak at gmail dot com [this message]
2015-02-23 10:00 ` rguenther at suse dot de

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-65136-4-j8A3Ld8twb@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).