[Bug target/88916] New: [x86] suboptimal code generated for integer comparisons joined with boolean operators

public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed

* [Bug target/88916] New: [x86] suboptimal code generated for integer comparisons joined with boolean operators
@ 2019-01-18 17:12 wojciech_mula at poczta dot onet.pl
  2021-08-11  5:19 ` [Bug tree-optimization/88916] " pinskia at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: wojciech_mula at poczta dot onet.pl @ 2019-01-18 17:12 UTC (permalink / raw)
  To: gcc-bugs

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 2445270 bytes --]

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

            Bug ID: 88916
           Summary: [x86] suboptimal code generated for integer
                    comparisons joined with boolean operators
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wojciech_mula at poczta dot onet.pl
  Target Milestone: ---

Let's consider these two simple, yet pretty useful functions:

--test.c---
int both_nonnegative(long a, long b) {
    return (a >= 0) && (b >= 0);
}

int both_nonzero(unsigned long a, unsigned long b) {
    return (a > 0) && (b > 0);
}
---eof--

$ gcc --version
gcc (Debian 8.2.0-13) 8.2.0

$ gcc -O3 test.c -march=skylake -S
$ cat test.s
both_nonnegative:
    notq    %rdi
    movq    %rdi, %rax
    notq    %rsi
    shrq    $63, %rax
    shrq    $63, %rsi
    andl    %esi, %eax
    ret

both_nonzero:
    testq   %rdi, %rdi
    setne   %al
    xorl    %edx, %edx
    testq   %rsi, %rsi
    setne   %dl
    andl    %edx, %eax
    ret

I checked different target machines (haswell, broadwell and cannonlake),
however the result remained the same. Also GCC trunk on godbolt.org 
produces the same assembly code.

The first function, `both_nonnegative`, can be rewritten as:

    (((unsigned long)(a) | (unsigned long)(b)) >> 63) ^ 1

yielding something like this:

    both_nonnegative:
        orq     %rsi, %rdi
        movq    %rdi, %rax
        shrq    $63, %rax
        xorl    $1, %eax
        ret

It's also possible to use this expression:
(long)(unsigned long)a | (unsigned long)b) < 0,
but the assembly output is almost the same.

The condition from `both_nonzero` can be expressed as:

    ((unsigned long)a | (unsigned long)b) != 0

GCC compiles it to:

    both_nonzero:
        xorl    %eax, %eax
        orq     %rsi, %rdi
        setne   %al
        retq
>From gcc-bugs-return-629785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 17:14:46 2019
Return-Path: <gcc-bugs-return-629785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115510 invoked by alias); 18 Jan 2019 17:14: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 115029 invoked by uid 55); 18 Jan 2019 17:14:35 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/88890] libbacktrace on 32-bit system with _FILE_OFFSET_BITS == 64
Date: Fri, 18 Jan 2019 17:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88890-4-lk7Gumphxm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88890-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88890-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: 2019-01/txt/msg02594.txt.bz2
Content-length: 766

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

--- Comment #1 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Fri Jan 18 17:13:59 2019
New Revision: 268082

URL: https://gcc.gnu.org/viewcvs?rev=268082&root=gcc&view=rev
Log:
        PR libbacktrace/88890
        * mmapio.c (backtrace_get_view): Change size parameter to
        uint64_t.  Check that value fits in size_t.
        * read.c (backtrace_get_view): Likewise.
        * internal.h (backtrace_get_view): Update declaration.
        * elf.c (elf_add): Pass shstrhdr->sh_size to backtrace_get_view.

Modified:
    trunk/libbacktrace/ChangeLog
    trunk/libbacktrace/elf.c
    trunk/libbacktrace/internal.h
    trunk/libbacktrace/mmapio.c
    trunk/libbacktrace/read.c
>From gcc-bugs-return-629786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 17:22:56 2019
Return-Path: <gcc-bugs-return-629786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125747 invoked by alias); 18 Jan 2019 17:22:56 -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 125610 invoked by uid 48); 18 Jan 2019 17:22:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Fri, 18 Jan 2019 17:22: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-WSxqfkEUAE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02595.txt.bz2
Content-length: 2246

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

--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, both the following patches should fix it IMHO, but no idea which one if any
is right.
With
--- gcc/config/rs6000/vsx.md.jj 2019-01-01 12:37:44.305529527 +0100
+++ gcc/config/rs6000/vsx.md    2019-01-18 18:07:37.194899062 +0100
@@ -4356,7 +4356,9 @@
   ""
   [(const_int 0)]
 {
-  rtx hi = gen_highpart (DFmode, operands[1]);
+  rtx hi = (BYTES_BIG_ENDIAN
+           ? gen_highpart (DFmode, operands[1])
+           : gen_lowpart (DFmode, operands[1]));
   rtx lo = (GET_CODE (operands[2]) == SCRATCH)
            ? gen_reg_rtx (DFmode)
            : operands[2];

the assembly changes:
--- reduction-3.s1      2019-01-18 18:05:14.313229730 +0100
+++ reduction-3.s2      2019-01-18 18:10:20.617233358 +0100
@@ -27,7 +27,7 @@ MAIN__._omp_fn.0:
        addi 9,9,16
        bdnz .L2
         # vec_extract to same register
-       lfd 12,-8(1)
+       lfd 12,-16(1)
        xsmaxdp 0,12,0
        stfd 0,0(10)
        blr
with:
--- gcc/config/rs6000/vsx.md.jj 2019-01-01 12:37:44.305529527 +0100
+++ gcc/config/rs6000/vsx.md    2019-01-18 18:16:30.680186709 +0100
@@ -4361,7 +4361,9 @@
            ? gen_reg_rtx (DFmode)
            : operands[2];

-  emit_insn (gen_vsx_extract_v2df (lo, operands[1], const1_rtx));
+  emit_insn (gen_vsx_extract_v2df (lo, operands[1],
+                                  BYTES_BIG_ENDIAN
+                                  ? const1_rtx : const0_rtx));
   emit_insn (gen_<VEC_reduc_rtx>df3 (operands[0], hi, lo));
   DONE;
 }
the assembly changes:
--- reduction-3.s1      2019-01-18 18:05:14.313229730 +0100
+++ reduction-3.s3      2019-01-18 18:17:18.977397458 +0100
@@ -26,7 +26,7 @@ MAIN__._omp_fn.0:
        xxpermdi 0,0,0,2
        addi 9,9,16
        bdnz .L2
-        # vec_extract to same register
+       xxpermdi 0,0,0,3
        lfd 12,-8(1)
        xsmaxdp 0,12,0
        stfd 0,0(10)

So just judging from this exact testcase, the first patch seems to be more
efficient, though still unsure about that, because it goes through memory in
either case, wouldn't it be better to emit a xxpermdi from 0 to 12 that swaps
the two elements instead of loading it from memory?
>From gcc-bugs-return-629787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 17:29:06 2019
Return-Path: <gcc-bugs-return-629787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5244 invoked by alias); 18 Jan 2019 17:29:05 -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 5049 invoked by uid 48); 18 Jan 2019 17:29:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Fri, 18 Jan 2019 17:29: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-n8eaUlzklb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02596.txt.bz2
Content-length: 1154

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

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And, if I disable that define_insn_and_split altogether (add 0 && to the
condition), the assembly change is:
--- reduction-3.s2      2019-01-18 18:19:42.184057246 +0100
+++ reduction-3.s4      2019-01-18 18:26:23.079506011 +0100
@@ -9,26 +9,16 @@ MAIN__._omp_fn.0:
        .cfi_startproc
        ld 10,0(3)
        lxvdsx 0,0,10
-       addi 9,1,-16
-       xxpermdi 0,0,0,2
-       stxvd2x 0,0,9
        ld 9,8(3)
        li 8,5
        mtctr 8
 .L2:
-       lxvd2x 0,0,9
-       addi 8,1,-16
-       lxvd2x 12,0,8
-       xxpermdi 12,12,12,2
-       xvmaxdp 0,12,0
-       xxpermdi 0,0,0,2
-       stxvd2x 0,0,8
-       xxpermdi 0,0,0,2
+       lxvd2x 12,0,9
+       xvmaxdp 0,0,12
        addi 9,9,16
        bdnz .L2
-        # vec_extract to same register
-       lfd 12,-16(1)
-       xsmaxdp 0,12,0
+       xxsldwi 12,0,0,2
+       xvmaxdp 0,12,0
        stfd 0,0(10)
        blr
        .long 0

which looks much better.  So, what is the reason for this
define_insn_and_split?  Is it useful for BYTES_BIG_ENDIAN only perhaps?
>From gcc-bugs-return-629788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 17:29:31 2019
Return-Path: <gcc-bugs-return-629788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6234 invoked by alias); 18 Jan 2019 17:29:31 -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 6092 invoked by uid 48); 18 Jan 2019 17:29:26 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/88890] libbacktrace on 32-bit system with _FILE_OFFSET_BITS == 64
Date: Fri, 18 Jan 2019 17:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status cc resolution
Message-ID: <bug-88890-4-DNl46x74AO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88890-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88890-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: 2019-01/txt/msg02597.txt.bz2
Content-length: 488

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

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |ian at airs dot com
         Resolution|---                         |FIXED

--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
Fixed.
>From gcc-bugs-return-629789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:01:07 2019
Return-Path: <gcc-bugs-return-629789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32467 invoked by alias); 18 Jan 2019 18:00:58 -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 32116 invoked by uid 48); 18 Jan 2019 18:00:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/80836] final binaries missing rpath despite all attempts to use the appropriate -Wl,-rpath= statement
Date: Fri, 18 Jan 2019 18:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-80836-4-wvhIS2uNBD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80836-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: 2019-01/txt/msg02598.txt.bz2
Content-length: 1083

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm unsure what exactly this report is about. The first half seems to be about
building GCC itself, and ensuring it can find the libs that GCC relies on,
right?

That's simple, just build the support libs in-tree so there are no runtime
dependencies on them. That's what the stackoverflow answer suggests, and is
what happens if you follow https://stackoverflow.com/a/10662297/981959 which
refers to https://gcc.gnu.org/wiki/InstallingGCC

In short, stop installing libgmp.so, libmpfr.so and libmpc.so in non-standard
locations and then trying to make GCC find them later. Just don't do that.
Everything's much easier if you don't do that.

The second half of this report seems to be about building your own programs
using GCC, and ensuring they can find GCC's runtime libs. I agree that an
option to add rpaths for GCC's own libs would be nice, but you can make it
happen automatically by installing a custom specs file that adds -rpath to the
*lib: spec.
>From gcc-bugs-return-629790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:02:33 2019
Return-Path: <gcc-bugs-return-629790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34566 invoked by alias); 18 Jan 2019 18:02:33 -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 34483 invoked by uid 55); 18 Jan 2019 18:02:29 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88892] [8/9 Regression] Double-to-float conversion uses wrong rounding mode when followed by memcpy
Date: Fri, 18 Jan 2019 18:02: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: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88892-4-m5rupZdVKH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88892-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88892-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: 2019-01/txt/msg02599.txt.bz2
Content-length: 687

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

--- Comment #13 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Author: segher
Date: Fri Jan 18 18:01:56 2019
New Revision: 268083

URL: https://gcc.gnu.org/viewcvs?rev=268083&root=gcc&view=rev
Log:
rs6000: Fix *movsi_from_df (PR88892)

The memory store instructions (stfs[u][x], stxssp[x]) can result in
garbage if the value to be stored isn't already a valid single
precision floating point number.  So we cannot use this here.


        PR target/88892
        * config/rs6000/rs6000.md (*movsi_from_df): Allow only register
        operands.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/rs6000/rs6000.md
>From gcc-bugs-return-629791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:08:21 2019
Return-Path: <gcc-bugs-return-629791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52582 invoked by alias); 18 Jan 2019 18:08: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 51789 invoked by uid 48); 18 Jan 2019 18:08:17 -0000
From: "kamleshbhalui at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Fri, 18 Jan 2019 18:08: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kamleshbhalui at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88877-4-yJpsHLDK0B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg02600.txt.bz2
Content-length: 1086

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

--- Comment #13 from Kamlesh Kumar <kamleshbhalui at gmail dot com> ---
(In reply to Alan Modra from comment #12)
> I suspect that the patch in comment #1 will break libcalls in other
> situations, eg.
> 
> void f1 (int y)
> {
>   extern double d;
>   d = y;
> }

Thanks Alan for pointing out.

One other patch i am thinking of is 

--- optabs.c    2019-01-18 23:28:09.822024657 +0530
+++ optabs.c    2019-01-18 23:28:44.805207684 +0530
@@ -4859,6 +4859,8 @@
       libfunc = convert_optab_libfunc (tab, GET_MODE (to), GET_MODE (from));
       gcc_assert (libfunc); 
       start_sequence ();
+      if(unsignedp && !is_narrower_int_mode (GET_MODE (from), SImode))
+        from = convert_to_mode (DImode, from, unsignedp);      
       value = emit_library_call_value (libfunc, NULL_RTX, LCT_CONST,
                                       GET_MODE (to), from, GET_MODE (from));
       insns = get_insns ();

Here, I am promoting mode early when we have signedness information.
Any thought on this?
>From gcc-bugs-return-629792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:12:16 2019
Return-Path: <gcc-bugs-return-629792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70053 invoked by alias); 18 Jan 2019 18:12:16 -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 69963 invoked by uid 48); 18 Jan 2019 18:12:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Fri, 18 Jan 2019 18:12: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88877-4-rsLDA1RibP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg02601.txt.bz2
Content-length: 1768

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Kamlesh Kumar from comment #13)
> (In reply to Alan Modra from comment #12)
> > I suspect that the patch in comment #1 will break libcalls in other
> > situations, eg.
> > 
> > void f1 (int y)
> > {
> >   extern double d;
> >   d = y;
> > }
> 
> Thanks Alan for pointing out.
> 
> One other patch i am thinking of is 
> 
> --- optabs.c	2019-01-18 23:28:09.822024657 +0530
> +++ optabs.c	2019-01-18 23:28:44.805207684 +0530
> @@ -4859,6 +4859,8 @@
>        libfunc = convert_optab_libfunc (tab, GET_MODE (to), GET_MODE (from));
>        gcc_assert (libfunc); 
>        start_sequence ();
> +      if(unsignedp && !is_narrower_int_mode (GET_MODE (from), SImode))
> +        from = convert_to_mode (DImode, from, unsignedp);      
>        value = emit_library_call_value (libfunc, NULL_RTX, LCT_CONST,
>  				       GET_MODE (to), from, GET_MODE (from));
>        insns = get_insns ();
> 
> Here, I am promoting mode early when we have signedness information.
> Any thought on this?

That is obviously wrong.  You are hardcoding behavior of -m64 powerpc64 target
in generic code.  Many targets in their ABIs don't care about bits beyond the
mode in which it is passed, others always sign extend, others always zero
extend, some pass arguments in SImode registers, others in DImode registers,
others in yet another kind of registers...
>From gcc-bugs-return-629793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:36:05 2019
Return-Path: <gcc-bugs-return-629793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110563 invoked by alias); 18 Jan 2019 18:36:05 -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 110464 invoked by uid 48); 18 Jan 2019 18:36:00 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/80836] final binaries missing rpath despite all attempts to use the appropriate -Wl,-rpath= statement
Date: Fri, 18 Jan 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-80836-4-WPemRxLF0j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80836-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: 2019-01/txt/msg02602.txt.bz2
Content-length: 828

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

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |egallager at gcc dot gnu.org

--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #5)
> 
> The second half of this report seems to be about building your own programs
> using GCC, and ensuring they can find GCC's runtime libs. I agree that an
> option to add rpaths for GCC's own libs would be nice, but you can make it
> happen automatically by installing a custom specs file that adds -rpath to
> the *lib: spec.

I thought custom specs files were no longer supported...
>From gcc-bugs-return-629794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:36:06 2019
Return-Path: <gcc-bugs-return-629794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110596 invoked by alias); 18 Jan 2019 18:36:05 -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 110501 invoked by uid 48); 18 Jan 2019 18:36:01 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88917] New: [8/9 Regression] Error: can't resolve `.text' {.text section} - `.LCFI2' {.text.unlikely section} with -fno-dwarf2-cfi-asm
Date: Fri, 18 Jan 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: assemble-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget attachments.created
Message-ID: <bug-88917-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: 2019-01/txt/msg02603.txt.bz2
Content-length: 2018

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

            Bug ID: 88917
           Summary: [8/9 Regression] Error: can't resolve `.text' {.text
                    section} - `.LCFI2' {.text.unlikely section} with
                    -fno-dwarf2-cfi-asm
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: assemble-failure
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

Created attachment 45465
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45465&action=edit
reduced testcase

Output:
$ x86_64-pc-linux-gnu-gcc -O2 -fno-dwarf2-cfi-asm
-mindirect-branch=thunk-inline testcase.c
/tmp/cc0YVyAa.s: Assembler messages:
/tmp/cc0YVyAa.s:104: Error: can't resolve `.text' {.text section} - `.LCFI2'
{.text.unlikely section}

$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-268059-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-268059-checking-yes-rtl-df-extra-amd64
Thread model: posix
gcc version 9.0.0 20190118 (experimental) (GCC) 

Interestingly, -fno-isolate-erroneous-paths-dereference prevents the problem,
even though the UB is not dereference, but potential divide by zero.
>From gcc-bugs-return-629795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:40:01 2019
Return-Path: <gcc-bugs-return-629795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6396 invoked by alias); 18 Jan 2019 18:40:01 -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 6284 invoked by uid 48); 18 Jan 2019 18:39:57 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88918] New: [meta-bug] x86 intrinsic issues
Date: Fri, 18 Jan 2019 18:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc dependson target_milestone cf_gcctarget
Message-ID: <bug-88918-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: 2019-01/txt/msg02604.txt.bz2
Content-length: 751

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

            Bug ID: 88918
           Summary: [meta-bug] x86 intrinsic issues
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: crazylht at gmail dot com, wei3.xiao at intel dot com,
                    xuepeng.guo at intel dot com
        Depends on: 71659
  Target Milestone: ---
            Target: i386,x86-64

This meta bug tracks all x86 intrinsic issues.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71659
[Bug 71659] _xgetbv intrinsic missing
>From gcc-bugs-return-629796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:45:56 2019
Return-Path: <gcc-bugs-return-629796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12122 invoked by alias); 18 Jan 2019 18:45:55 -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 104035 invoked by uid 48); 18 Jan 2019 18:45:23 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83618] _rdpid_u32 doesn't work on 64-bit targets as gas expects the 64-bit register
Date: Fri, 18 Jan 2019 18:45: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: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-83618-4-VyEAIPDN1Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83618-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83618-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: 2019-01/txt/msg02605.txt.bz2
Content-length: 478

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |8.0

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 8.
>From gcc-bugs-return-629797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:49:08 2019
Return-Path: <gcc-bugs-return-629797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48558 invoked by alias); 18 Jan 2019 18:49:07 -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 48372 invoked by uid 48); 18 Jan 2019 18:48:58 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80862] [x86] Wrong rounding results for some test cases
Date: Fri, 18 Jan 2019 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: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-80862-4-c6zwAEMczQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80862-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: 2019-01/txt/msg02606.txt.bz2
Content-length: 478

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |8.0

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 8.
>From gcc-bugs-return-629798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:55:56 2019
Return-Path: <gcc-bugs-return-629798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57497 invoked by alias); 18 Jan 2019 18:55:56 -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 57337 invoked by uid 48); 18 Jan 2019 18:55:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Fri, 18 Jan 2019 18:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88044-4-ZjNF41HR9s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-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: 2019-01/txt/msg02607.txt.bz2
Content-length: 3302

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I've put logging into tree-ssa-loop-niters.c, looking for when before/after
r266171 code would make a difference in the returned value, the only case it
triggers on is (all types integer(kind=4) i.e. signed 32-bit integer):
code LE_EXPR
iv0->base 0
iv0->step 0
iv1->base -1
iv1->step 1
every_iteration false
The loop starts with:
  <bb 7> [local count: 8656061039]:
  # n_63 = PHI <0(6), _28(23)>
  _19 = n_63 + -1;
and ends with
  _28 = n_63 + 1;
  if (_28 == 4)
    goto <bb 21>; [12.36%]
  else
    goto <bb 23>; [87.64%]

  <bb 23> [local count: 7582748748]:
  goto <bb 7>; [100.00%]
and besides the exit at the end has also:
  <bb 16> [local count: 3548985018]:
  if (_19 > 0)
    goto <bb 17>; [0.04%]
  else
    goto <bb 28>; [99.96%]

  <bb 17> [local count: 1419591]:
  _gfortran_stop_numeric (1, 0);

  <bb 18> [local count: 5106238449]:
  if (_19 < 0)
    goto <bb 19>; [0.04%]
  else
    goto <bb 29>; [99.96%]

  <bb 29> [local count: 5104195957]:
  goto <bb 20>; [100.00%]

  <bb 19> [local count: 2042498]:
  _gfortran_stop_numeric (2, 0);
in the middle, so two other loop exits.  But, neither bb16, nor bb18 are
executed every iteration, if they were, then because _19 is -1 in the first
iteration would always stop 2 and not iterate further.

We have:
  /* If the test is not executed every iteration, wrapping may make the test
     to pass again.
     TODO: the overflow case can be still used as unreliable estimate of upper
     bound.  But we have no API to pass it down to number of iterations code
     and, at present, it will not use it anyway.  */
  if (!every_iteration
      && (!iv0->no_overflow || !iv1->no_overflow
          || code == NE_EXPR || code == EQ_EXPR))
    return false;
at the start, but that doesn't trigger here, because code is not equality
comparison and no_overflow is set on both IVs.  If there would be an overflow,
then maybe it would be right to derive number of iterations from that.
But the condition that returns true is that iv0->base code iv1->base is false,
if that isn't done in every iteration, it means nothing for the number of
iteration analysis.

The following patch works for me:
2019-01-18  Jakub Jelinek  <jakub@redhat.com>

        PR tree-optimization/88044
        * tree-ssa-loop-niter.c (number_of_iterations_cond): If condition
        is false in the first iteration, but !every_iteration, return false
        instead of true with niter->niter zero.

--- gcc/tree-ssa-loop-niter.c.jj        2019-01-10 11:43:02.254577008 +0100
+++ gcc/tree-ssa-loop-niter.c   2019-01-18 19:51:00.245504728 +0100
@@ -1824,6 +1824,8 @@ number_of_iterations_cond (struct loop *
   tree tem = fold_binary (code, boolean_type_node, iv0->base, iv1->base);
   if (tem && integer_zerop (tem))
     {
+      if (!every_iteration)
+       return false;
       niter->niter = build_int_cst (unsigned_type_for (type), 0);
       niter->max = 0;
       return true;
>From gcc-bugs-return-629799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 18:56:01 2019
Return-Path: <gcc-bugs-return-629799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58154 invoked by alias); 18 Jan 2019 18:56:01 -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 57473 invoked by uid 48); 18 Jan 2019 18:55:55 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/68923] SSE/AVX movq load (_mm_cvtsi64_si128) not being folded into pmovzx
Date: Fri, 18 Jan 2019 18:56: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.3.0
X-Bugzilla-Keywords: missed-optimization, ssemmx
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-68923-4-CJR6pt3F2g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68923-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: 2019-01/txt/msg02608.txt.bz2
Content-length: 1585

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |9.0

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 9:

[hjl@gnu-cfl-1 gcc]cat x.c
#include <immintrin.h>
#include <stdint.h>
#define USE_MOVQ
__m256 load_bytes_to_m256(uint8_t *p)
{
#ifdef  USE_MOVQ  // compiles to an actual movq then pmovzx xmm,xmm with gcc
-O3
    __m128i small_load = _mm_cvtsi64_si128( *(uint64_t*)p );
#else  // loadu compiles to a 128b load with gcc -O0, potentially segfaulting
    __m128i small_load = _mm_loadu_si128( (__m128i*)p );
#endif

    __m256i intvec = _mm256_cvtepu8_epi32( small_load );
    return _mm256_cvtepi32_ps(intvec);
}
[hjl@gnu-cfl-1 gcc]$ ./xgcc -B./ -S -O3 x.c  -march=haswell
[hjl@gnu-cfl-1 gcc]$ cat x.s
        .file   "x.c"
        .text
        .p2align 4
        .globl  load_bytes_to_m256
        .type   load_bytes_to_m256, @function
load_bytes_to_m256:
.LFB5186:
        .cfi_startproc
        vpmovzxbd       (%rdi), %ymm0
        vcvtdq2ps       %ymm0, %ymm0
        ret
        .cfi_endproc
.LFE5186:
        .size   load_bytes_to_m256, .-load_bytes_to_m256
        .ident  "GCC: (GNU) 9.0.0 20190118 (experimental)"
        .section        .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 gcc]$
>From gcc-bugs-return-629800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:05:42 2019
Return-Path: <gcc-bugs-return-629800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115871 invoked by alias); 18 Jan 2019 19:05:41 -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 109003 invoked by uid 48); 18 Jan 2019 19:05:37 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88918] [meta-bug] x86 intrinsic issues
Date: Fri, 18 Jan 2019 19:05: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
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: bug_status cf_reconfirmed_on dependson everconfirmed
Message-ID: <bug-88918-4-4JvQ5gBwfj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88918-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88918-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: 2019-01/txt/msg02609.txt.bz2
Content-length: 2814

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-18
         Depends on|                            |49300, 53687, 55894, 56253,
                   |                            |59071, 65744, 68211, 87558,
                   |                            |85236, 85058, 80517, 78921,
                   |                            |78782, 77633, 68924, 68923,
                   |                            |68484
     Ever confirmed|0                           |1


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49300
[Bug 49300] [x86] Missing SSE4.1 intrinsic function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53687
[Bug 53687] _mm_cmpistri generates redundant movslq %ecx,%rcx on x86-64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55894
[Bug 55894] No constant propagation in Intel intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56253
[Bug 56253] fp-contract does not work with SSE and AVX FMAs (neither FMA4 nor
FMA3)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59071
[Bug 59071] sse2 intrinsics and constant expressions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65744
[Bug 65744] Some AVX512 instrinsics take __mmask16 instead of __mmask8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68211
[Bug 68211] Free __m128d subreg of double
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68484
[Bug 68484] _mm_storel_epi64((__m128i *)x, m); does nothing if "x" is a
"volatile" ptr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68923
[Bug 68923] SSE/AVX movq load (_mm_cvtsi64_si128) not being folded into pmovzx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68924
[Bug 68924] No intrinsic for x86  `MOVQ m64, %xmm`  in 32bit mode.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77633
[Bug 77633] AVX512: shuffle intrinsic has incorrect signature when
optimizations are enabled
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78782
[Bug 78782] [x86] _mm_loadu_si64 intrinsic missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78921
[Bug 78921] SSE/AVX shuffle intrinsics uses ia32_builtins instead of
__builtin_shuffle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80517
[Bug 80517] [missed optimization] constant propagation through Intel intrinsics
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85058
[Bug 85058] Builtin-functions for -mbmi2 documented with wrong names
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85236
[Bug 85236] missing _mm256_atan2_ps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87558
[Bug 87558] Missing _mm_storeu_si64() intrinsic
>From gcc-bugs-return-629801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:26:39 2019
Return-Path: <gcc-bugs-return-629801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82272 invoked by alias); 18 Jan 2019 19:26:39 -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 82216 invoked by uid 48); 18 Jan 2019 19:26:33 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88919] New: New test case gcc.dg/vect/pr88903-1.c in r268076 fails
Date: Fri, 18 Jan 2019 19:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88919-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: 2019-01/txt/msg02610.txt.bz2
Content-length: 3238

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

            Bug ID: 88919
           Summary: New test case gcc.dg/vect/pr88903-1.c in r268076 fails
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

Executing on host: /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vect/pr88903-1.c   
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never   -maltivec -mpower8-vector -ftree-vectorize
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details  -lm  -o
./pr88903-1.exe    (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vect/pr88903-1.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -maltivec -mpower8-vector -ftree-vectorize
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details -lm -o
./pr88903-1.exe
PASS: gcc.dg/vect/pr88903-1.c (test for excess errors)
Setting LD_LIBRARY_PATH to
:/home/seurer/gcc/build/gcc-test2/gcc::/home/seurer/gcc/build/gcc-test2/gcc:/home/seurer/gcc/build/gcc-test2/./gmp/.libs:/home/seurer/gcc/build/gcc-test2/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test2/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-test2/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test2/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test2/./prev-mpc/src/.libs:/home/seurer/gcc/build/gcc-test2/./isl/.libs:/home/seurer/gcc/build/gcc-test2/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.2.0/lib64
Execution timeout is: 300
spawn [open ...]
FAIL: gcc.dg/vect/pr88903-1.c execution test


seurer@makalu-lp1:~/gcc/build/gcc-test2$
/home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vect/pr88903-1.c   
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never  -flto -ffat-lto-objects -maltivec -mpower8-vector
-ftree-vectorize -fno-vect-cost-model -fno-common -g -O2
-fdump-tree-vect-details  -lm  -o ./pr88903-1.exe

seurer@makalu-lp1:~/gcc/build/gcc-test2$ gdb ./pr88903-1.exe
(gdb) run
Starting program: /home/seurer/gcc/build/gcc-test2/./pr88903-1.exe 

Program received signal SIGABRT, Aborted.
0x00003fffb7cd247c in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:55
55        return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
(gdb) where
#0  0x00003fffb7cd247c in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:55
#1  0x00003fffb7cd4688 in __GI_abort () at abort.c:90
#2  0x0000000010000670 in main () at
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vect/pr88903-1.c:24

int
main()
{
  check_vect ();
  for (int i = 0; i < 1024; ++i)
    x[i] = i;
  foo ();
  for (int i = 0; i < 1024; ++i)
    if (x[i] != i << (i/2+1))
      __builtin_abort ();  // line 24
  return 0;
}
>From gcc-bugs-return-629802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:26:56 2019
Return-Path: <gcc-bugs-return-629802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83212 invoked by alias); 18 Jan 2019 19:26:55 -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 83026 invoked by uid 48); 18 Jan 2019 19:26:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88917] [8/9 Regression] Error: can't resolve `.text' {.text section} - `.LCFI2' {.text.unlikely section} with -fno-dwarf2-cfi-asm
Date: Fri, 18 Jan 2019 19:26: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: 9.0
X-Bugzilla-Keywords: assemble-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed
Message-ID: <bug-88917-4-70HQroDodK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88917-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88917-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: 2019-01/txt/msg02611.txt.bz2
Content-length: 726

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-18
                 CC|                            |jakub at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
   Target Milestone|---                         |8.3
     Ever confirmed|0                           |1

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with my r264651.  Will have a look.
>From gcc-bugs-return-629803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:41:22 2019
Return-Path: <gcc-bugs-return-629803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6352 invoked by alias); 18 Jan 2019 19:41: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 6255 invoked by uid 48); 18 Jan 2019 19:41:10 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] New: [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Fri, 18 Jan 2019 19:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88920-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: 2019-01/txt/msg02612.txt.bz2
Content-length: 24822

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

            Bug ID: 88920
           Summary: [9 regression] GCC is not configured to support
                    amdgcn-unknown-amdhsa as offload target
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

This error is generated scores of times, more than 100, when running a make
check on powerpc64 (both BE and LE):

Executing on host: /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/ offload_gcn35072.c   
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never  -foffload=amdgcn-unknown-amdhsa -S -o
offload_gcn35072.s    (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/ offload_gcn35072.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -foffload=amdgcn-unknown-amdhsa -S -o
offload_gcn35072.s
xgcc: fatal error: GCC is not configured to support amdgcn-unknown-amdhsa as
offload target
compilation terminated.
compiler exited with status 1


It occurs all over the place but it does not appear to cause any test cases to
fail.  I first noticed it when looking at a different problem in r268076 but I
do not think it is tied to that revision.  I am trying to see if I can narrow
down when it started.


seurer@genoa:~/gcc/build/gcc-trunk$ grep "GCC is not configured to support
amdgcn-unknown-amdhsa as offload target" `find . -name "*.log"`     
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gcc/gcc.log:xgcc: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/gfortran/gfortran.log:gfortran: fatal error: GCC is not
configured to support amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./gcc/testsuite/g++/g++.log:xg++: fatal error: GCC is not configured to support
amdgcn-unknown-amdhsa as offload target
./powerpc64le-unknown-linux-gnu/libitm/testsuite/libitm.log:xgcc: fatal error:
GCC is not configured to support amdgcn-unknown-amdhsa as offload target
./powerpc64le-unknown-linux-gnu/libatomic/testsuite/libatomic.log:xgcc: fatal
error: GCC is not configured to support amdgcn-unknown-amdhsa as offload target
./powerpc64le-unknown-linux-gnu/libgomp/testsuite/libgomp.log:xgcc: fatal
error: GCC is not configured to support amdgcn-unknown-amdhsa as offload target
>From gcc-bugs-return-629804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:43:01 2019
Return-Path: <gcc-bugs-return-629804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8146 invoked by alias); 18 Jan 2019 19:43:01 -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 8075 invoked by uid 48); 18 Jan 2019 19:42:56 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/88911] No "did you mean" for incorrect -dumpspecs option
Date: Fri, 18 Jan 2019 19:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-88911-4-KhN9TnlhnH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88911-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88911-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: 2019-01/txt/msg02613.txt.bz2
Content-length: 675

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-18
                 CC|                            |dmalcolm at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |dmalcolm at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed; am working on a patch.
>From gcc-bugs-return-629805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:48:48 2019
Return-Path: <gcc-bugs-return-629805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15446 invoked by alias); 18 Jan 2019 19:48:47 -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 15411 invoked by uid 48); 18 Jan 2019 19:48:42 -0000
From: "weeks at iastate dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87326] [F18] Support the NEW_INDEX= specifier in the FORM TEAM statement
Date: Fri, 18 Jan 2019 19:48: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: weeks at iastate dot edu
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-87326-4-p5Pp1dc4Hf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87326-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87326-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: 2019-01/txt/msg02614.txt.bz2
Content-length: 295

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

--- Comment #2 from Nathan Weeks <weeks at iastate dot edu> ---
I think that would be appropriate, especially since I submitted a patch that
attempts to address those two simultaneously:

https://gcc.gnu.org/ml/fortran/2019-01/msg00131.html
>From gcc-bugs-return-629806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 19:51:36 2019
Return-Path: <gcc-bugs-return-629806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23896 invoked by alias); 18 Jan 2019 19:51:36 -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 23849 invoked by uid 48); 18 Jan 2019 19:51:31 -0000
From: "weeks at iastate dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87939] [F18] Support STAT= and ERRMSG= specifiers to CRITICAL and TEAM statements
Date: Fri, 18 Jan 2019 19:51: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: weeks at iastate dot edu
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:
Message-ID: <bug-87939-4-nlwgg5kEe3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87939-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: 2019-01/txt/msg02615.txt.bz2
Content-length: 234

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

--- Comment #2 from Nathan Weeks <weeks at iastate dot edu> ---
The following patch attempts to address this issue & pr87326:

https://gcc.gnu.org/ml/fortran/2019-01/msg00131.html
>From gcc-bugs-return-629807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 20:36:20 2019
Return-Path: <gcc-bugs-return-629807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79805 invoked by alias); 18 Jan 2019 20:36: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 79682 invoked by uid 48); 18 Jan 2019 20:36:15 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] [9 regression] initializer_list and explicit ctor
Date: Fri, 18 Jan 2019 20:36: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88875-4-sx8zj03WSj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88875-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: 2019-01/txt/msg02616.txt.bz2
Content-length: 423

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 20:36:35 2019
Return-Path: <gcc-bugs-return-629808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80622 invoked by alias); 18 Jan 2019 20:36:34 -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 80525 invoked by uid 55); 18 Jan 2019 20:36:29 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] [9 regression] initializer_list and explicit ctor
Date: Fri, 18 Jan 2019 20:36: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88875-4-sIKpDR1gjN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88875-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: 2019-01/txt/msg02617.txt.bz2
Content-length: 914

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

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Fri Jan 18 20:35:57 2019
New Revision: 268085

URL: https://gcc.gnu.org/viewcvs?rev=268085&root=gcc&view=rev
Log:
        PR c++/88875 - error with explicit list constructor.

In my patch for CWG issue 2267, I changed reference_binding to clear
CONSTRUCTOR_IS_DIRECT_INIT on the argument init-list.  But that breaks if
there's another candidate for which CONSTRUCTOR_IS_DIRECT_INIT is correct.
So instead, let's encode in the conversion that we want to override the
flag.

        * call.c (reference_binding): Don't modify EXPR.  Set
        need_temporary_p on the ck_user conversion for a temporary.
        (convert_like_real): Check it.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/initlist-explicit2.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/call.c
>From gcc-bugs-return-629809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 20:51:02 2019
Return-Path: <gcc-bugs-return-629809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125591 invoked by alias); 18 Jan 2019 20:51:02 -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 125492 invoked by uid 48); 18 Jan 2019 20:50:57 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Fri, 18 Jan 2019 20:51: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-FopIJWf7YJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-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: 2019-01/txt/msg02618.txt.bz2
Content-length: 161

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

--- Comment #13 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Is this ready to be submitted?
>From gcc-bugs-return-629810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 20:52:41 2019
Return-Path: <gcc-bugs-return-629810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127141 invoked by alias); 18 Jan 2019 20:52:40 -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 127043 invoked by uid 48); 18 Jan 2019 20:52:37 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59071] sse2 intrinsics and constant expressions
Date: Fri, 18 Jan 2019 20:52: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.8.2
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work resolution target_milestone cf_known_to_fail
Message-ID: <bug-59071-4-Dx31I55Eao@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59071-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: 2019-01/txt/msg02619.txt.bz2
Content-length: 596

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

Marc Glisse <glisse at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
      Known to work|                            |6.5.0
         Resolution|---                         |FIXED
   Target Milestone|---                         |6.0
      Known to fail|                            |5.5.0

--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
Seems to work now.
>From gcc-bugs-return-629811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 20:52:41 2019
Return-Path: <gcc-bugs-return-629811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127286 invoked by alias); 18 Jan 2019 20:52:41 -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 127085 invoked by uid 48); 18 Jan 2019 20:52:37 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88918] [meta-bug] x86 intrinsic issues
Date: Fri, 18 Jan 2019 20:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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: bug_status resolution
Message-ID: <bug-88918-4-1rA47meHbz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88918-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88918-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: 2019-01/txt/msg02620.txt.bz2
Content-length: 466

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88918
Bug 88918 depends on bug 59071, which changed state.

Bug 59071 Summary: sse2 intrinsics and constant expressions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59071

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
>From gcc-bugs-return-629812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 20:56:15 2019
Return-Path: <gcc-bugs-return-629812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 391 invoked by alias); 18 Jan 2019 20:56:15 -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 131016 invoked by uid 48); 18 Jan 2019 20:56:10 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88560] [9 Regression] armv8_2-fp16-move-1.c and related regressions after r266385
Date: Fri, 18 Jan 2019 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88560-4-9bMfAkyvQY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88560-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: 2019-01/txt/msg02621.txt.bz2
Content-length: 3501

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

--- Comment #5 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
We have too many tests checking expected generated code.  We should more focus
on overall effect of the change.  SPEC would be a good criterium although it is
hard to check SPEC for each patch.

I've checked the generated code of arm8_2-fp16-move-1.c and found that in most
cases GCC generates better code with the patch:

@@ -80,7 +80,6 @@ test_load_store_1:
        @ frame_needed = 0, uses_anonymous_args = 0
        @ link register save eliminated.
        lsl     r1, r1, #1
-       vmov.f16        s0, r3  @ __fp16
        ldrh    r3, [r2, r1]    @ __fp16
        strh    r3, [r0, r1]    @ __fp16
        bx      lr
@@ -97,10 +96,11 @@ test_load_store_2:
        @ link register save eliminated.
        add     r1, r1, #2
        lsl     r1, r1, #1
+       add     r3, r2, r1
        add     r0, r0, r1
-       ldrh    r3, [r2, r1]    @ __fp16
+       vld1.16 {d0[0]}, [r3]
+       vmov.f16        r3, s0  @ __fp16
        strh    r3, [r0, #-4]   @ __fp16
-       vmov.f16        s0, r3  @ __fp16
        bx      lr
        .size   test_load_store_2, .-test_load_store_2
        .align  2
@@ -176,14 +176,13 @@ test_select_5:
        @ frame_needed = 0, uses_anonymous_args = 0
        @ link register save eliminated.
        vcvtb.f32.f16   s0, s0
-       vcvtb.f32.f16   s14, s1
-       vmov    s15, s1 @ __fp16
-       vcmpe.f32       s0, s14
+       vcvtb.f32.f16   s15, s1
+       vcmpe.f32       s0, s15
        vmrs    APSR_nzcv, FPSCR
        bmi     .L17
-       vmov    s15, s2 @ __fp16
+       vmov    s1, s2  @ __fp16
 .L17:
-       vmov    s0, s15 @ __fp16
+       vmov    s0, s1  @ __fp16
        bx      lr
        .size   test_select_5, .-test_select_5
        .align  2
@@ -197,14 +196,13 @@ test_select_6:
        @ frame_needed = 0, uses_anonymous_args = 0
        @ link register save eliminated.
        vcvtb.f32.f16   s0, s0
-       vcvtb.f32.f16   s14, s1
-       vmov    s15, s1 @ __fp16
-       vcmpe.f32       s0, s14
+       vcvtb.f32.f16   s15, s1
+       vcmpe.f32       s0, s15
        vmrs    APSR_nzcv, FPSCR
        bls     .L19
-       vmov    s15, s2 @ __fp16
+       vmov    s1, s2  @ __fp16
 .L19:
-       vmov    s0, s15 @ __fp16
+       vmov    s0, s1  @ __fp16
        bx      lr
        .size   test_select_6, .-test

The only worse code is for test_load_store_2.  The culprit insn is 

(insn 12 10 16 2 (set (mem:HF (plus:SI (reg/f:SI 121)
                (const_int -4 [0xfffffffffffffffc])) [1 *_6+0 S2 A16])
        (reg:HF 116 [ <retval> ])) "b.i":4:8 653 {*movhf_vfp_fp16}
     (expr_list:REG_DEAD (reg/f:SI 121)
        (nil)))

Before the patch p116 had GENERAL_REGS class and after the patch it has
VFP_LO_REGS.  The memory move cost for VFP_LO_REGS is small although the insn
for VFP_LO_REGS prohibits memory with this kind address.

There are a few ways to fix this:
  1. give RA correct cost for store VFP_LO_REGS into given memory which means
adding a new hook taking specific memory rtx
  2. check insn constraints to modify cost in some way
  3. try to reload address instead of memory itself

I prefer the last solution although it requires changes in sensitive part of
LRA and will require a lot testing on a few targets.  So I am working on the
patch.

In any case, I don't think the PR should have P1.  P3 or even P4 would be more
accurate estimation (please see my top comments).
>From gcc-bugs-return-629813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:29:36 2019
Return-Path: <gcc-bugs-return-629813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76608 invoked by alias); 18 Jan 2019 21:29:36 -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 76446 invoked by uid 55); 18 Jan 2019 21:29:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87520] [8 Regression] ODR violations in std::make_shared when mixing -fno-rtti and -frtti
Date: Fri, 18 Jan 2019 21:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87520-4-RrhIice4UR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87520-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87520-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: 2019-01/txt/msg02622.txt.bz2
Content-length: 3682

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

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Jan 18 21:28:48 2019
New Revision: 268086

URL: https://gcc.gnu.org/viewcvs?rev=268086&root=gcc&view=rev
Log:
PR libstdc++/88782 avoid ODR problems in std::make_shared

The old version of _Sp_counted_ptr_inplace::_M_get_deleter (up to GCC
8.2.0) expects to be passed a real std::typeinfo object, so mixing that
with the new definition of the __shared_ptr constructor (which always
passes the fake tag) leads to accessing the fake object as a real
std::typeinfo. Instead of trying to make it safe to mix the old and new
definitions, just stop using that function. By passing a reference to
__shared_ptr::_M_ptr to the __shared_count constructor it can be set
directly, without needing to obtain the pointer via the _M_get_deleter
back-channel. This avoids a virtual dispatch (which fixes PR 87514).

This means that code built against new libstdc++ headers doesn't use
_M_get_deleter at all, and so make_shared works the same whether RTTI is
enabled or not.

Also change _M_get_deleter so that it checks for a real type_info object
even when RTTI is disabled, by calling a library function. Unless
libstdc++ itself is built without RTTI that library function will be
able to test if it's the right type_info. This means the new definition
of _M_get_deleter can handle both the fake type_info tag and a real
type_info object, even if built without RTTI.

If linking to objects built against older versions of libstdc++ then if
all objects use -frtti or all use -fno-rtti, then the caller of
_M_get_deleter and the definition of _M_get_deleter will be consistent
and it will work. If mixing -frtti with -fno-rtti it can still fail if
the linker picks an old definition of _M_get_deleter and an old
__shared_ptr constructor that are incompatible. In that some or all
objects might need to be recompiled.

        PR libstdc++/87514
        PR libstdc++/87520
        PR libstdc++/88782
        * config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export new symbol.
        * include/bits/shared_ptr.h
        (shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...))
        (allocate_shared): Change to use new tag type.
        * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_eq):
        Declare new member function.
        (_Sp_alloc_shared_tag): Define new type.
        (_Sp_counted_ptr_inplace): Declare __shared_count<_Lp> as a friend.
        (_Sp_counted_ptr_inplace::_M_get_deleter) [!__cpp_rtti]: Use
        _Sp_make_shared_tag::_S_eq to check type_info.
        (__shared_count(Ptr, Deleter),__shared_count(Ptr, Deleter, Alloc)):
        Constrain to prevent being called with _Sp_alloc_shared_tag.
        (__shared_count(_Sp_make_shared_tag, const _Alloc&, Args&&...)):
        Replace constructor with ...
        (__shared_count(Tp*&, _Sp_alloc_shared_tag<_Alloc>, Args&&...)): Use
        reference parameter so address of the new object can be returned to
        the caller. Obtain the allocator from the tag type.
        (__shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...)): Replace
        constructor with ...
        (__shared_ptr(_Sp_alloc_shared_tag<Alloc>, Args&&...)): Pass _M_ptr
        to the __shared_count constructor.
        (__allocate_shared): Change to use new tag type.
        * src/c++11/shared_ptr.cc (_Sp_make_shared_tag::_S_eq): Define.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/config/abi/pre/gnu.ver
    trunk/libstdc++-v3/include/bits/shared_ptr.h
    trunk/libstdc++-v3/include/bits/shared_ptr_base.h
    trunk/libstdc++-v3/src/c++11/shared_ptr.cc
>From gcc-bugs-return-629815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:29:36 2019
Return-Path: <gcc-bugs-return-629815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76652 invoked by alias); 18 Jan 2019 21:29:36 -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 76436 invoked by uid 55); 18 Jan 2019 21:29:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] [8/9 Regression] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc > 8.2
Date: Fri, 18 Jan 2019 21:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88782-4-jhGMyuSMC2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-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: 2019-01/txt/msg02624.txt.bz2
Content-length: 3681

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Jan 18 21:28:48 2019
New Revision: 268086

URL: https://gcc.gnu.org/viewcvs?rev=268086&root=gcc&view=rev
Log:
PR libstdc++/88782 avoid ODR problems in std::make_shared

The old version of _Sp_counted_ptr_inplace::_M_get_deleter (up to GCC
8.2.0) expects to be passed a real std::typeinfo object, so mixing that
with the new definition of the __shared_ptr constructor (which always
passes the fake tag) leads to accessing the fake object as a real
std::typeinfo. Instead of trying to make it safe to mix the old and new
definitions, just stop using that function. By passing a reference to
__shared_ptr::_M_ptr to the __shared_count constructor it can be set
directly, without needing to obtain the pointer via the _M_get_deleter
back-channel. This avoids a virtual dispatch (which fixes PR 87514).

This means that code built against new libstdc++ headers doesn't use
_M_get_deleter at all, and so make_shared works the same whether RTTI is
enabled or not.

Also change _M_get_deleter so that it checks for a real type_info object
even when RTTI is disabled, by calling a library function. Unless
libstdc++ itself is built without RTTI that library function will be
able to test if it's the right type_info. This means the new definition
of _M_get_deleter can handle both the fake type_info tag and a real
type_info object, even if built without RTTI.

If linking to objects built against older versions of libstdc++ then if
all objects use -frtti or all use -fno-rtti, then the caller of
_M_get_deleter and the definition of _M_get_deleter will be consistent
and it will work. If mixing -frtti with -fno-rtti it can still fail if
the linker picks an old definition of _M_get_deleter and an old
__shared_ptr constructor that are incompatible. In that some or all
objects might need to be recompiled.

        PR libstdc++/87514
        PR libstdc++/87520
        PR libstdc++/88782
        * config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export new symbol.
        * include/bits/shared_ptr.h
        (shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...))
        (allocate_shared): Change to use new tag type.
        * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_eq):
        Declare new member function.
        (_Sp_alloc_shared_tag): Define new type.
        (_Sp_counted_ptr_inplace): Declare __shared_count<_Lp> as a friend.
        (_Sp_counted_ptr_inplace::_M_get_deleter) [!__cpp_rtti]: Use
        _Sp_make_shared_tag::_S_eq to check type_info.
        (__shared_count(Ptr, Deleter),__shared_count(Ptr, Deleter, Alloc)):
        Constrain to prevent being called with _Sp_alloc_shared_tag.
        (__shared_count(_Sp_make_shared_tag, const _Alloc&, Args&&...)):
        Replace constructor with ...
        (__shared_count(Tp*&, _Sp_alloc_shared_tag<_Alloc>, Args&&...)): Use
        reference parameter so address of the new object can be returned to
        the caller. Obtain the allocator from the tag type.
        (__shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...)): Replace
        constructor with ...
        (__shared_ptr(_Sp_alloc_shared_tag<Alloc>, Args&&...)): Pass _M_ptr
        to the __shared_count constructor.
        (__allocate_shared): Change to use new tag type.
        * src/c++11/shared_ptr.cc (_Sp_make_shared_tag::_S_eq): Define.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/config/abi/pre/gnu.ver
    trunk/libstdc++-v3/include/bits/shared_ptr.h
    trunk/libstdc++-v3/include/bits/shared_ptr_base.h
    trunk/libstdc++-v3/src/c++11/shared_ptr.cc
>From gcc-bugs-return-629814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:29:36 2019
Return-Path: <gcc-bugs-return-629814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76616 invoked by alias); 18 Jan 2019 21:29:36 -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 76469 invoked by uid 55); 18 Jan 2019 21:29:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87514] std::make_shared could avoid virtual call to _Sp_counted_ptr_inplace::_M_get_deleter()
Date: Fri, 18 Jan 2019 21:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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:
Message-ID: <bug-87514-4-PDPia9wGez@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87514-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87514-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: 2019-01/txt/msg02623.txt.bz2
Content-length: 3681

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Jan 18 21:28:48 2019
New Revision: 268086

URL: https://gcc.gnu.org/viewcvs?rev=268086&root=gcc&view=rev
Log:
PR libstdc++/88782 avoid ODR problems in std::make_shared

The old version of _Sp_counted_ptr_inplace::_M_get_deleter (up to GCC
8.2.0) expects to be passed a real std::typeinfo object, so mixing that
with the new definition of the __shared_ptr constructor (which always
passes the fake tag) leads to accessing the fake object as a real
std::typeinfo. Instead of trying to make it safe to mix the old and new
definitions, just stop using that function. By passing a reference to
__shared_ptr::_M_ptr to the __shared_count constructor it can be set
directly, without needing to obtain the pointer via the _M_get_deleter
back-channel. This avoids a virtual dispatch (which fixes PR 87514).

This means that code built against new libstdc++ headers doesn't use
_M_get_deleter at all, and so make_shared works the same whether RTTI is
enabled or not.

Also change _M_get_deleter so that it checks for a real type_info object
even when RTTI is disabled, by calling a library function. Unless
libstdc++ itself is built without RTTI that library function will be
able to test if it's the right type_info. This means the new definition
of _M_get_deleter can handle both the fake type_info tag and a real
type_info object, even if built without RTTI.

If linking to objects built against older versions of libstdc++ then if
all objects use -frtti or all use -fno-rtti, then the caller of
_M_get_deleter and the definition of _M_get_deleter will be consistent
and it will work. If mixing -frtti with -fno-rtti it can still fail if
the linker picks an old definition of _M_get_deleter and an old
__shared_ptr constructor that are incompatible. In that some or all
objects might need to be recompiled.

        PR libstdc++/87514
        PR libstdc++/87520
        PR libstdc++/88782
        * config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export new symbol.
        * include/bits/shared_ptr.h
        (shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...))
        (allocate_shared): Change to use new tag type.
        * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_eq):
        Declare new member function.
        (_Sp_alloc_shared_tag): Define new type.
        (_Sp_counted_ptr_inplace): Declare __shared_count<_Lp> as a friend.
        (_Sp_counted_ptr_inplace::_M_get_deleter) [!__cpp_rtti]: Use
        _Sp_make_shared_tag::_S_eq to check type_info.
        (__shared_count(Ptr, Deleter),__shared_count(Ptr, Deleter, Alloc)):
        Constrain to prevent being called with _Sp_alloc_shared_tag.
        (__shared_count(_Sp_make_shared_tag, const _Alloc&, Args&&...)):
        Replace constructor with ...
        (__shared_count(Tp*&, _Sp_alloc_shared_tag<_Alloc>, Args&&...)): Use
        reference parameter so address of the new object can be returned to
        the caller. Obtain the allocator from the tag type.
        (__shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...)): Replace
        constructor with ...
        (__shared_ptr(_Sp_alloc_shared_tag<Alloc>, Args&&...)): Pass _M_ptr
        to the __shared_count constructor.
        (__allocate_shared): Change to use new tag type.
        * src/c++11/shared_ptr.cc (_Sp_make_shared_tag::_S_eq): Define.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/config/abi/pre/gnu.ver
    trunk/libstdc++-v3/include/bits/shared_ptr.h
    trunk/libstdc++-v3/include/bits/shared_ptr_base.h
    trunk/libstdc++-v3/src/c++11/shared_ptr.cc
>From gcc-bugs-return-629816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:33:48 2019
Return-Path: <gcc-bugs-return-629816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86590 invoked by alias); 18 Jan 2019 21:33:48 -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 82573 invoked by uid 48); 18 Jan 2019 21:33:41 -0000
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87106] Group move and destruction of the source, where possible, for speed
Date: Fri, 18 Jan 2019 21:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: arthur.j.odwyer at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-87106-4-gOZc8mNKKm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87106-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: 2019-01/txt/msg02625.txt.bz2
Content-length: 642

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

--- Comment #15 from Arthur O'Dwyer <arthur.j.odwyer at gmail dot com> ---
@Marc, it only now occurs to me that if libstdc++ uses
`__is_trivially_relocatable` as its userspace type-trait name, then GCC won't
be able to use `__is_trivially_relocatable(T)` as the name of its compiler
builtin. (It would be analogous to if libstdc++ had used
`__is_trivially_copyable` as the name of a type-trait.)
Is there any chance that you could rename `__is_trivially_relocatable` to
`__is_trivially_relocatablex` or `__has_trivial_relocatability` or something
like that? Is it too late? I hope not.
>From gcc-bugs-return-629817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:35:31 2019
Return-Path: <gcc-bugs-return-629817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90645 invoked by alias); 18 Jan 2019 21:35:30 -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 90599 invoked by uid 48); 18 Jan 2019 21:35:25 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88921] New: inconsistent warning on a power-of-2 memcpy with out-of-bounds offset
Date: Fri, 18 Jan 2019 21:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88921-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: 2019-01/txt/msg02626.txt.bz2
Content-length: 4913

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

            Bug ID: 88921
           Summary: inconsistent warning on a power-of-2 memcpy with
                    out-of-bounds offset
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

None of the obviously invalid calls to memcpy in the test case below is
diagnosed on common targets that fold memcpy calls with small power-of-2 sizes
into MEM_REF.  They are, however, diagnosed on targets like arm-eabi that don't
fold such calls.

This not makes writing tests for these kinds of warnings tedious (they may pass
or fail on common targets used for development only to fail on secondary
targets), it also makes developing portable software difficult when it compiles
cleanly during development but fails on targets for which builds are done only
rarely (usually because of scarcity of target boards).

GCC should issue warnings for invalid constructs consistently and regardless of
the target.

$ cat t.c && gcc -O2 -S -Wall -Wextra -fdump-tree-wrestrict=/dev/stdout t.c 
extern char a[];

void f (const char *s, __SIZE_TYPE__ i)
{
  i = __PTRDIFF_MAX__ - 1;

  __builtin_memcpy (a + i, s, 2);
}

void g (const char *s, __PTRDIFF_TYPE__ i)
{
  i = __PTRDIFF_MAX__ - 1;

  __builtin_memcpy (a + i, s, 2);
}

void h (const char *s, __PTRDIFF_TYPE__ i)
{
  if (i < __PTRDIFF_MAX__ - 1)
    i = __PTRDIFF_MAX__ - 1;

  __builtin_memcpy (a + i, s, 2);
}

;; Function f (f, funcdef_no=0, decl_uid=1908, cgraph_uid=1, symbol_order=0)

f (const char * s, long unsigned int i)
{
  short unsigned int _3;

  <bb 2> [local count: 1073741824]:
  _3 = MEM[(char * {ref-all})s_2(D)];
  MEM[(char * {ref-all})&a + 9223372036854775806B] = _3;
  return;

}



;; Function g (g, funcdef_no=1, decl_uid=1912, cgraph_uid=2, symbol_order=1)

g (const char * s, long int i)
{
  short unsigned int _3;

  <bb 2> [local count: 1073741824]:
  _3 = MEM[(char * {ref-all})s_2(D)];
  MEM[(char * {ref-all})&a + 9223372036854775806B] = _3;
  return;

}



;; Function h (h, funcdef_no=2, decl_uid=1916, cgraph_uid=3, symbol_order=2)

h (const char * s, long int i)
{
  sizetype i.1_1;
  void * _2;
  short unsigned int _7;

  <bb 2> [local count: 1073741824]:
  i_4 = MAX_EXPR <i_3(D), 9223372036854775806>;
  i.1_1 = (sizetype) i_4;
  _2 = &a + i.1_1;
  _7 = MEM[(char * {ref-all})s_6(D)];
  MEM[(char * {ref-all})_2] = _7;
  return;

}


Contrast that to:

$ /build/arm-none-eabi/gcc-svn/gcc/xgcc -B /build/arm-none-eabi/gcc-svn/gcc -O2
-S -Wall -Wextra -fdump-tree-wrestrict=/dev/stdout t.c 

;; Function f (f, funcdef_no=0, decl_uid=4141, cgraph_uid=1, symbol_order=0)

t.c: In function â€˜fâ€™:
t.c:7:3: warning: â€˜__builtin_memcpyâ€™ pointer overflow between offset 2147483646
and size 2 accessing array â€˜aâ€™ with type â€˜char[]â€™ [-Warray-bounds]
    7 |   __builtin_memcpy (a + i, s, 2);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c:1:13: note: array â€˜aâ€™ declared here
    1 | extern char a[];
      |             ^
f (const char * s, unsigned int i)
{
  <bb 2> [local count: 1073741824]:
  __builtin_memcpy (&MEM[(void *)&a + 2147483646B], s_2(D), 2);
  return;

}



;; Function g (g, funcdef_no=1, decl_uid=4145, cgraph_uid=2, symbol_order=1)

t.c: In function â€˜gâ€™:
t.c:14:3: warning: â€˜__builtin_memcpyâ€™ pointer overflow between offset
2147483646 and size 2 accessing array â€˜aâ€™ with type â€˜char[]â€™ [-Warray-bounds]
   14 |   __builtin_memcpy (a + i, s, 2);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c:1:13: note: array â€˜aâ€™ declared here
    1 | extern char a[];
      |             ^
g (const char * s, int i)
{
  <bb 2> [local count: 1073741824]:
  __builtin_memcpy (&MEM[(void *)&a + 2147483646B], s_2(D), 2);
  return;

}



;; Function h (h, funcdef_no=2, decl_uid=4149, cgraph_uid=3, symbol_order=2)

t.c: In function â€˜hâ€™:
t.c:22:3: warning: â€˜__builtin_memcpyâ€™ pointer overflow between offset
[2147483646, 2147483647] and size 2 accessing array â€˜aâ€™ with type â€˜char[]â€™
[-Warray-bounds]
   22 |   __builtin_memcpy (a + i, s, 2);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c:1:13: note: array â€˜aâ€™ declared here
    1 | extern char a[];
      |             ^
h (const char * s, int i)
{
  sizetype i.1_1;
  void * _2;

  <bb 2> [local count: 1073741824]:
  i_4 = MAX_EXPR <i_3(D), 2147483646>;
  i.1_1 = (sizetype) i_4;
  _2 = &a + i.1_1;
  __builtin_memcpy (_2, s_6(D), 2);
  return;

}
>From gcc-bugs-return-629818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:39:39 2019
Return-Path: <gcc-bugs-return-629818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94661 invoked by alias); 18 Jan 2019 21:39: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 94573 invoked by uid 48); 18 Jan 2019 21:39:33 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Fri, 18 Jan 2019 21:39: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-KzwXtkaqki@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-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: 2019-01/txt/msg02627.txt.bz2
Content-length: 333

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

--- Comment #14 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to JÃ¼rgen Reuter from comment #13)
> Is this ready to be submitted?

Already done - https://gcc.gnu.org/ml/fortran/2019-01/msg00135.html .

I'll commit tomorrow unless somebody has furher to add.
>From gcc-bugs-return-629819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:43:20 2019
Return-Path: <gcc-bugs-return-629819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102612 invoked by alias); 18 Jan 2019 21:43:19 -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 102536 invoked by uid 48); 18 Jan 2019 21:43:15 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88560] [9 Regression] armv8_2-fp16-move-1.c and related regressions after r266385
Date: Fri, 18 Jan 2019 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88560-4-4zXMEx1NLL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88560-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: 2019-01/txt/msg02628.txt.bz2
Content-length: 899

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

--- Comment #6 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #5)
> We have too many tests checking expected generated code.  We should more
> focus on overall effect of the change.  SPEC would be a good criterium
> although it is hard to check SPEC for each patch.
> 
> I've checked the generated code of arm8_2-fp16-move-1.c and found that in
> most cases GCC generates better code with the patch:
> 
> @@ -80,7 +80,6 @@ test_load_store_1:
>         @ frame_needed = 0, uses_anonymous_args = 0
>         @ link register save eliminated.
>         lsl     r1, r1, #1
> -       vmov.f16        s0, r3  @ __fp16
>         ldrh    r3, [r2, r1]    @ __fp16
>         strh    r3, [r0, r1]    @ __fp16
>         bx      lr

When I tested it, this test added that vmov, not removed it - see comment #2.
>From gcc-bugs-return-629820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:43:36 2019
Return-Path: <gcc-bugs-return-629820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103422 invoked by alias); 18 Jan 2019 21:43:36 -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 103340 invoked by uid 48); 18 Jan 2019 21:43:30 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88922] New: Merge identical constants with different modes
Date: Fri, 18 Jan 2019 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88922-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: 2019-01/txt/msg02629.txt.bz2
Content-length: 1156

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

            Bug ID: 88922
           Summary: Merge identical constants with different modes
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: glisse at gcc dot gnu.org
  Target Milestone: ---

#include <stdint.h>
typedef int64_t v64 __attribute__((vector_size(16)));
typedef int32_t v32 __attribute__((vector_size(16)));
typedef int16_t v16 __attribute__((vector_size(16)));

int main(){
  volatile v64 x = {1,2};
  volatile v32 y = {1,0,2,0};
  volatile v16 z = {1,0,0,0,2,0,0,0};
}

        movdqa  .LC0(%rip), %xmm0
        xorl    %eax, %eax
        movaps  %xmm0, -56(%rsp)
        movdqa  .LC1(%rip), %xmm0
        movaps  %xmm0, -40(%rsp)
        movdqa  .LC2(%rip), %xmm0
        movaps  %xmm0, -24(%rsp)

gcc fails to notice that the 3 constants are the same. I would have expected
the constant pool to be handled as an untyped collection of bits at the end.
>From gcc-bugs-return-629822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:52:30 2019
Return-Path: <gcc-bugs-return-629822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28045 invoked by alias); 18 Jan 2019 21:52:30 -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 25468 invoked by uid 48); 18 Jan 2019 21:52:26 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
Date: Fri, 18 Jan 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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: bug_status resolution
Message-ID: <bug-88443-4-spmDaFr6ch@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88443-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88443-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: 2019-01/txt/msg02631.txt.bz2
Content-length: 508

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
Bug 88443 depends on bug 79220, which changed state.

Bug 79220 Summary: missing -Wstringop-overflow= on a memcpy overflow with a small power-of-2 size
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79220

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
>From gcc-bugs-return-629821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:52:30 2019
Return-Path: <gcc-bugs-return-629821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27884 invoked by alias); 18 Jan 2019 21:52:29 -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 24521 invoked by uid 48); 18 Jan 2019 21:52:24 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/79220] missing -Wstringop-overflow= on a memcpy overflow with a small power-of-2 size
Date: Fri, 18 Jan 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work resolution target_milestone cf_known_to_fail
Message-ID: <bug-79220-4-YCRzAN1gVS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79220-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79220-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: 2019-01/txt/msg02630.txt.bz2
Content-length: 1255

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
      Known to work|                            |9.0
         Resolution|---                         |FIXED
   Target Milestone|---                         |9.0
      Known to fail|                            |7.3.0, 8.2.0

--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
GCC 9 diagnoses both calls with -Warray-bounds.  With it disabled, it then
issues the expected -Wstringop-overflow:

$ gcc -O2 -S -Wno-array-bounds t.c t.c: In function â€˜fâ€™:
t.c:7:3: warning: â€˜memcpyâ€™ writing 8 bytes into a region of size 3 overflows
the destination [-Wstringop-overflow=]
    7 |   memcpy (d, "0123456789", 8);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c: In function â€˜gâ€™:
t.c:12:3: warning: â€˜memcpyâ€™ writing 8 bytes into a region of size 3 overflows
the destination [-Wstringop-overflow=]
   12 |   memcpy (d, s, 8);
      |   ^~~~~~~~~~~~~~~~

This was fixed for GCC 9 in r268037.
>From gcc-bugs-return-629823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 21:56:33 2019
Return-Path: <gcc-bugs-return-629823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73977 invoked by alias); 18 Jan 2019 21:56:33 -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 70663 invoked by uid 48); 18 Jan 2019 21:56:29 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88921] inconsistent warning on a power-of-2 memcpy with out-of-bounds offset
Date: Fri, 18 Jan 2019 21:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords see_also blocked
Message-ID: <bug-88921-4-Cfnq4PNcSB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88921-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88921-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: 2019-01/txt/msg02632.txt.bz2
Content-length: 1132

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=79220
             Blocks|                            |56456

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
See pr79220 where a similar problem was already fixed.  This still doesn't work
because memcpy calls with a small power-of-2 size continue to be folded when
the out-of-bounds offset is not detected (the detection happens too early,
before the value of the non-constant offset, and especially its range, is
known).

The only way to solve this without delaying the folding is to also check
MEM_REF expressions for out-of-bounds offsets.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
[Bug 56456] [meta-bug] bogus/missing -Warray-bounds
>From gcc-bugs-return-629824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 22:05:08 2019
Return-Path: <gcc-bugs-return-629824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60175 invoked by alias); 18 Jan 2019 22:05:08 -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 60003 invoked by uid 48); 18 Jan 2019 22:05:01 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87106] Group move and destruction of the source, where possible, for speed
Date: Fri, 18 Jan 2019 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-87106-4-oKtayFBLpf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87106-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: 2019-01/txt/msg02633.txt.bz2
Content-length: 1206

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

--- Comment #16 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Arthur O'Dwyer from comment #15)
> @Marc, it only now occurs to me that if libstdc++ uses
> `__is_trivially_relocatable` as its userspace type-trait name, then GCC
> won't be able to use `__is_trivially_relocatable(T)` as the name of its
> compiler builtin. (It would be analogous to if libstdc++ had used
> `__is_trivially_copyable` as the name of a type-trait.)
> Is there any chance that you could rename `__is_trivially_relocatable` to
> `__is_trivially_relocatablex` or `__has_trivial_relocatability` or something
> like that? Is it too late? I hope not.

The name __is_trivially_relocatable is currently undocumented, it is an
implementation detail and users should not specialize it (or at least they
should be ready for it to break very easily). It can be renamed at any point if
convenient, say if/when gcc implements a builtin with the same name. Or is the
issue that clang already has such a builtin, and it now conflicts with
libstdc++? In that case I agree we should rename it. I don't care much about
the name, see what the maintainers are happy with...
>From gcc-bugs-return-629825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 22:08:52 2019
Return-Path: <gcc-bugs-return-629825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71989 invoked by alias); 18 Jan 2019 22:08:52 -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 66609 invoked by uid 48); 18 Jan 2019 22:08:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Fri, 18 Jan 2019 22:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88920-4-q1WDMs5itQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02634.txt.bz2
Content-length: 214

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Have you configured gcc with --enable-offload-targets= that includes
amdgcn-unknown-amdhsa ?
>From gcc-bugs-return-629826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 22:14:25 2019
Return-Path: <gcc-bugs-return-629826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15677 invoked by alias); 18 Jan 2019 22:14:25 -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 8786 invoked by uid 48); 18 Jan 2019 22:14:17 -0000
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87106] Group move and destruction of the source, where possible, for speed
Date: Fri, 18 Jan 2019 22:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: arthur.j.odwyer at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-87106-4-NfsyVt44zo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87106-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: 2019-01/txt/msg02635.txt.bz2
Content-length: 1925

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

--- Comment #17 from Arthur O'Dwyer <arthur.j.odwyer at gmail dot com> ---
(In reply to Marc Glisse from comment #16)
> (In reply to Arthur O'Dwyer from comment #15)
> > @Marc, it only now occurs to me that if libstdc++ uses
> > `__is_trivially_relocatable` as its userspace type-trait name, then GCC
> > won't be able to use `__is_trivially_relocatable(T)` as the name of its
> > compiler builtin. (It would be analogous to if libstdc++ had used
> > `__is_trivially_copyable` as the name of a type-trait.)
> > Is there any chance that you could rename `__is_trivially_relocatable` to
> > `__is_trivially_relocatablex` or `__has_trivial_relocatability` or something
> > like that? Is it too late? I hope not.
> 
> The name __is_trivially_relocatable is currently undocumented, it is an
> implementation detail and users should not specialize it (or at least they
> should be ready for it to break very easily). It can be renamed at any point
> if convenient, say if/when gcc implements a builtin with the same name. Or
> is the issue that clang already has such a builtin, and it now conflicts
> with libstdc++? In that case I agree we should rename it. I don't care much
> about the name, see what the maintainers are happy with...

Agreed users should be ready for the library trait to break.

Clang doesn't currently have such a builtin, but I am proposing it in
https://reviews.llvm.org/D50119 (and I would rather rename the libstdc++ detail
than the proposed Clang builtin).

My concern is that if GCC/Clang EVER implement such a builtin, then that
(newer) version of GCC/Clang would forever be unable to build this (older)
version of libstdc++. I think that's not the end of the world, but I think we
ought to preemptively avoid the situation if it's cheap to do so. I should have
brought this up earlier, but as I said, it just dawned on me today.
>From gcc-bugs-return-629827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 22:20:04 2019
Return-Path: <gcc-bugs-return-629827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18414 invoked by alias); 18 Jan 2019 22:20:03 -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 18252 invoked by uid 48); 18 Jan 2019 22:19:57 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Fri, 18 Jan 2019 22:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88920-4-yeyTEtd4Fh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02636.txt.bz2
Content-length: 395

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

--- Comment #2 from seurer at gcc dot gnu.org ---
The configure is pretty simple:

/home/seurer/gcc/gcc-test2/configure
--prefix=/home/seurer/gcc/install/gcc-test2 --enable-languages=c,fortran,c++
--with-cpu=power8 --disable-bootstrap
--with-as=/home/seurer/binutils/install/bin/as
--with-ld=/home/seurer/binutils/install/bin/ld
>From gcc-bugs-return-629828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 22:59:45 2019
Return-Path: <gcc-bugs-return-629828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110413 invoked by alias); 18 Jan 2019 22:59:45 -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 110295 invoked by uid 48); 18 Jan 2019 22:59:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Fri, 18 Jan 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88920-4-ZnhkvfUmhP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02637.txt.bz2
Content-length: 1389

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ams at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ugh, it happens everywhere.  I guess the problem is that unlike the other
effective targets like check_effective_target_offload_nvptx etc.,
check_effective_target_offload_gcn is used in
check_effective_target_llvm_binutils and that one is used on pretty much
everything:
    # Complain about blank lines in the output (PR other/69006)
    global allow_blank_lines
    if { !$allow_blank_lines && ![check_effective_target_llvm_binutils]} {
        set num_blank_lines [llength [regexp -all -inline "\n\n" $text]]
        if { $num_blank_lines } {
            global testname_with_flags
            fail "$testname_with_flags $num_blank_lines blank line(s) in
output"
        }
        set allow_blank_lines 0
    }
First of all, I fail to see why we care about offload to gcn here, we don't
really have any scan-assembler for offloading stuff, that is done only when
linking.

If the above is really needed for some reason (please explain), then it should
be at least cached, so that it is not invoked 420 times.
>From gcc-bugs-return-629829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 18 23:05:34 2019
Return-Path: <gcc-bugs-return-629829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116980 invoked by alias); 18 Jan 2019 23:05:33 -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 116857 invoked by uid 48); 18 Jan 2019 23:05:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Fri, 18 Jan 2019 23:05: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-87064-4-18wydqC2pO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02638.txt.bz2
Content-length: 749

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1

--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I've gathered some statistics, the vsx_reduc_<VEC_reduc_name>_v2df
define_insn_and_split is never used during powerpc64-linux bootstrap and
-m32/-m64 testing and during powerpc64le-linux bootstrap and testing is only
triggered on the miscompiled reduction-3.f90.  That doesn't mean it can't be
useful for big endian, I just don't know how to trigger it to verify if it is
beneficial or not.
>From gcc-bugs-return-629830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 01:08:21 2019
Return-Path: <gcc-bugs-return-629830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14678 invoked by alias); 19 Jan 2019 01:08: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 14561 invoked by uid 48); 19 Jan 2019 01:08:16 -0000
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88897] Bogus maybe-uninitialized warning on class field
Date: Sat, 19 Jan 2019 01:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rafael at espindo dot la
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88897-4-aSXP0m1dpU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88897-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88897-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: 2019-01/txt/msg02639.txt.bz2
Content-length: 1078

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

--- Comment #3 from Rafael Avila de Espindola <rafael at espindo dot la> ---
(In reply to Andrew Pinski from comment #2)
> Some of the time, the uninitialized is due to using the object after the
> lifetime of the object has gone out of scope.  I have not checked if that is
> the case here but I would not be suprised.

Thanks! This may very well be the case.

This reduces further to

struct deleter {
  deleter(deleter &&x) {}
  deleter(deleter &) = default;
};
struct temporary_buffer {
  temporary_buffer(temporary_buffer &) = default;
  char *_buffer = nullptr;
  deleter _deleter;
};
void foo123(temporary_buffer);
struct future_state {
  union any {
    any() {}
    temporary_buffer value;
  } _u;
  void forward_to() { foo123(_u.value); }
};
void then3() {
  future_state _local_state;
  _local_state.forward_to();
}


which has a real uninitialized use. I am looking again at the unreduced test
case to see if that was the original issue.

More context in the warning message would have been awesome! :-)
>From gcc-bugs-return-629831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 01:26:53 2019
Return-Path: <gcc-bugs-return-629831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33663 invoked by alias); 19 Jan 2019 01:26:53 -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 33616 invoked by uid 48); 19 Jan 2019 01:26:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88293] [9 Regression] ICE on C++11 code: in build_target_expr_with_type, at cp/tree.c:793
Date: Sat, 19 Jan 2019 01:26: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88293-4-8VboUmKiNA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88293-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88293-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: 2019-01/txt/msg02640.txt.bz2
Content-length: 727

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
An even simpler test case:

  struct A
  { 
    constexpr A () { }
  };

  const A &a = (A (), A ());

The assertion below fails:

/* Build a TARGET_EXPR using INIT to initialize a new temporary of the
   indicated TYPE.  */

tree
build_target_expr_with_type (tree init, tree type, tsubst_flags_t complain)
{
  gcc_assert (!VOID_TYPE_P (type));
>From gcc-bugs-return-629832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 06:57:41 2019
Return-Path: <gcc-bugs-return-629832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64284 invoked by alias); 19 Jan 2019 06:57:40 -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 64240 invoked by uid 48); 19 Jan 2019 06:57:36 -0000
From: "antanubis at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88923] New: abi::__cxa_demangle segfault on a specific string
Date: Sat, 19 Jan 2019 06:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antanubis at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88923-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: 2019-01/txt/msg02641.txt.bz2
Content-length: 2655

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

            Bug ID: 88923
           Summary: abi::__cxa_demangle segfault on a specific string
           Product: gcc
           Version: 7.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: antanubis at gmail dot com
  Target Milestone: ---

I use "dump_syms" util from Google Breakpad to extract debug symbols from my
binaries and at some version it started segfaulting. I've found the exact
string on which the call to abi::__cxa_demangle crashes and it reproduces in a
standalone example (name 'test.cpp'):

#include <cxxabi.h>
#include <iostream>
int main() {
        const char *symbol =
"_ZNSt11_Tuple_implILm0EJN3rpl8producerIN4base5flagsIN11MTPDchannel4FlagEEENS0_8no_errorEZNS0_7details10map_helperIZN4Data18FlagsValueWithMaskINSA_5FlagsIS6_Lj2147486693EE6ChangeES7_ZNS8_11then_helperISE_S7_ZNKS0_12event_streamISE_E6eventsEvEUlRKT_E_EclISE_S7_ZNS0_6singleISE_EEDaOSI_EUlSK_E_SE_S7_EEDaONS1_ISI_T0_T1_EEEUlSK_E_EEDaSU_NSI_4TypeEEUlRKSE_E0_EclISE_S7_ZNS8_13filter_helperIZNSB_ISE_S7_SV_EEDaSU_SW_EUlSY_E_EclISE_S7_SV_vEEDaSU_EUlSK_E_S6_EEDaSU_EUlSK_E_EENS1_IbS7_ZNS9_IZNSA_15SingleFlagValueINSC_INS3_IN19MTPDchatAdminRights4FlagEEELj4294967295EE6ChangeES7_ZNSF_IS1E_S7_ZNKSG_IS1E_E6eventsEvEUlSK_E_EclIS1E_S7_ZNSO_IS1E_EEDaSP_EUlSK_E_S1E_S7_EEDaSU_EUlSK_E_EEDaSU_NSI_4EnumEEUlS1C_E_EclIS1C_S7_ZNS9_IZNSB_IS1E_S7_S1K_EEDaSU_SW_EUlRKS1E_E0_EclIS1E_S7_ZNS12_IZNSB_IS1E_S7_S1K_EEDaSU_SW_EUlS1Q_E_EclIS1E_S7_S1K_vEEDaSU_EUlSK_E_S1C_EEDaSU_EUlSK_E_bEEDaSU_EUlSK_E_EENS1_IbS7_ZNS9_IZNS19_INSC_INS3_IN20MTPDchatBannedRights4FlagEEELj4294967295EE6ChangeES7_ZNSF_IS25_S7_ZNKSG_IS25_E6eventsEvEUlSK_E_EclIS25_S7_ZNSO_IS25_EEDaSP_EUlSK_E_S25_S7_EEDaSU_EUlSK_E_EEDaSU_S1L_EUlS23_E_EclIS23_S7_ZNS9_IZNSB_IS25_S7_S2B_EEDaSU_SW_EUlRKS25_E0_EclIS25_S7_ZNS12_IZNSB_IS25_S7_S2B_EEDaSU_SW_EUlS2G_E_EclIS25_S7_S2B_vEEDaSU_EUlSK_E_S23_EEDaSU_EUlSK_E_bEEDaSU_EUlSK_E_EES2Q_EED2Ev.lto_priv.19273";
        int status = 0;
        char* demangled_c =
                abi::__cxa_demangle(symbol, NULL, NULL, &status);
        if (status == 0) {
                std::cout << demangled_c << std::endl;
        } else {
                std::cout << "Error: " << status << std::endl;
        }
        if (demangled_c) {
                free(reinterpret_cast<void*>(demangled_c));
        }
        return 0;
}

This program compiled with "gcc test.cpp -lstdc++" crashes for me on gcc 7.4 on
Ubuntu 14.04 and on gcc 7.3 on Ubuntu 18.04.
>From gcc-bugs-return-629833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 07:00:04 2019
Return-Path: <gcc-bugs-return-629833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67504 invoked by alias); 19 Jan 2019 07:00:03 -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 66427 invoked by uid 48); 19 Jan 2019 06:59:59 -0000
From: "antanubis at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88923] abi::__cxa_demangle segfault on a specific string
Date: Sat, 19 Jan 2019 07:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antanubis at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88923-4-PF93jWXq5J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88923-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: 2019-01/txt/msg02642.txt.bz2
Content-length: 360

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

--- Comment #1 from Vasilii Babich <antanubis at gmail dot com> ---
Created attachment 45466
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45466&action=edit
test.cpp to reproduce the segfault

This program crashes for me when compiled with "gcc test.cpp -lstdc++" on both
gcc 7.3 and gcc 7.4.
>From gcc-bugs-return-629834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 08:08:30 2019
Return-Path: <gcc-bugs-return-629834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118042 invoked by alias); 19 Jan 2019 08:08:30 -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 117967 invoked by uid 48); 19 Jan 2019 08:08:25 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80265] __builtin_{memcmp,memchr,strlen} are not usable in constexpr functions
Date: Sat, 19 Jan 2019 08:08: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: 7.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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:
Message-ID: <bug-80265-4-qC87y3AeET@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80265-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80265-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: 2019-01/txt/msg02643.txt.bz2
Content-length: 998

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

--- Comment #33 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #8)
> I think there was a bug report in the last month or so asking for some
> builtin to detect when we're in a constexpr context.

Now that we have (__builtin_)is_constant_evaluated, does __constant_string_p
still serve a purpose, or could we replace it? ISTR __constant_string_p was
causing various issues (including PR 86590).

(In reply to Jason Merrill from comment #16)
> (In reply to Marc Glisse from comment #13)
> > it seems better than abusing __builtin_constant_p, which is getting
> > contradictory requirements from its various uses:
> > - constexpr (forces very early lowering)
> 
> I'm not sure what you mean here; constexpr specifically delays lowering
> within a constexpr function until we're actually trying to evaluate to a
> constant value.

Bug 85746 for instance, where the problem is how hard we should "try".
>From gcc-bugs-return-629835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 08:33:09 2019
Return-Path: <gcc-bugs-return-629835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33411 invoked by alias); 19 Jan 2019 08:33:09 -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 33354 invoked by uid 48); 19 Jan 2019 08:33:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80265] __builtin_{memcmp,memchr,strlen} are not usable in constexpr functions
Date: Sat, 19 Jan 2019 08:33: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: 7.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: attachments.created
Message-ID: <bug-80265-4-yKW7PHy3ZL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80265-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80265-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: 2019-01/txt/msg02644.txt.bz2
Content-length: 421

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

--- Comment #34 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45467
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45467&action=edit
gcc9-pr86590.patch

Untested patch to use __builtin_is_constant_evaluated() here.  I believe it
should help, the inliner should be able to see smaller inline functions and
could make better decisions.
>From gcc-bugs-return-629836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 08:43:49 2019
Return-Path: <gcc-bugs-return-629836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53853 invoked by alias); 19 Jan 2019 08:43:49 -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 53768 invoked by uid 55); 19 Jan 2019 08:43:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88902] ICE: Segmentation fault (in DFS::DFS_write_tree_body)
Date: Sat, 19 Jan 2019 08:43: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: 9.0
X-Bugzilla-Keywords: GC, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88902-4-wVc3f22gSK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88902-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88902-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: 2019-01/txt/msg02645.txt.bz2
Content-length: 635

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jan 19 08:43:12 2019
New Revision: 268091

URL: https://gcc.gnu.org/viewcvs?rev=268091&root=gcc&view=rev
Log:
        PR fortran/88902
        * trans-decl.c (gfc_get_symbol_decl): Don't add length to function
        or parent function if it has been added there already.

        * gfortran.dg/pr88902.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/pr88902.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-decl.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 08:44:58 2019
Return-Path: <gcc-bugs-return-629837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56958 invoked by alias); 19 Jan 2019 08:44:57 -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 56881 invoked by uid 48); 19 Jan 2019 08:44:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88902] ICE: Segmentation fault (in DFS::DFS_write_tree_body)
Date: Sat, 19 Jan 2019 08:44: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: 9.0
X-Bugzilla-Keywords: GC, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88902-4-XmxO11Dr0n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88902-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88902-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: 2019-01/txt/msg02646.txt.bz2
Content-length: 146

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-629838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 09:37:58 2019
Return-Path: <gcc-bugs-return-629838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7884 invoked by alias); 19 Jan 2019 09:37:58 -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 7821 invoked by uid 48); 19 Jan 2019 09:37:54 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80265] __builtin_{memcmp,memchr,strlen} are not usable in constexpr functions
Date: Sat, 19 Jan 2019 09:37: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: 7.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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:
Message-ID: <bug-80265-4-nbKMst4uDh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80265-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80265-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: 2019-01/txt/msg02647.txt.bz2
Content-length: 378

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

--- Comment #35 from Marc Glisse <glisse at gcc dot gnu.org> ---
I just noticed that Jonathan has already written such a patch in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86590#c28 but didn't commit it
(maybe because is_constant_evaluated was not committed yet, or because it was
not sufficient to solve that PR).
>From gcc-bugs-return-629839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 09:43:19 2019
Return-Path: <gcc-bugs-return-629839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76490 invoked by alias); 19 Jan 2019 09:43:19 -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 63768 invoked by uid 48); 19 Jan 2019 09:43:14 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86590] Codegen is poor when passing std::string by value with _GLIBCXX_EXTERN_TEMPLATE undefined
Date: Sat, 19 Jan 2019 09:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86590-4-Twv1vth89Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86590-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86590-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: 2019-01/txt/msg02648.txt.bz2
Content-length: 360

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

--- Comment #31 from Marc Glisse <glisse at gcc dot gnu.org> ---
Adding "inline" to _M_construct does convince the inliner to proceed, but I
don't know if that would cause too much bloat in other code, it would be best
if IPA somehow guessed that this case is interesting without having its hand
forced.
>From gcc-bugs-return-629840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 11:04:05 2019
Return-Path: <gcc-bugs-return-629840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56966 invoked by alias); 19 Jan 2019 11:04: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 56864 invoked by uid 55); 19 Jan 2019 11:04:00 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Sat, 19 Jan 2019 11:04: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-PG8FJFlLlw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-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: 2019-01/txt/msg02649.txt.bz2
Content-length: 494

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

--- Comment #15 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sat Jan 19 11:03:28 2019
New Revision: 268092

URL: https://gcc.gnu.org/viewcvs?rev=268092&root=gcc&view=rev
Log:
2019-01-17  Thomas Koenig  <tkoenig@gcc.gnu.org>

        PR fortran/88871
        * resolve.c (resolve_ref): Fix logic for removal of
        reference.


Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/resolve.c
>From gcc-bugs-return-629841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 11:04:51 2019
Return-Path: <gcc-bugs-return-629841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57969 invoked by alias); 19 Jan 2019 11:04:51 -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 57928 invoked by uid 48); 19 Jan 2019 11:04:47 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Sat, 19 Jan 2019 11:04: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88871-4-0s8tMXsgk0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-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: 2019-01/txt/msg02650.txt.bz2
Content-length: 437

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #16 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed, closing.
>From gcc-bugs-return-629842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 12:32:42 2019
Return-Path: <gcc-bugs-return-629842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125674 invoked by alias); 19 Jan 2019 12:32:41 -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 125629 invoked by uid 48); 19 Jan 2019 12:32:35 -0000
From: "yangyibiao at nju dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/83599] [GCOV] A If TRUE statement lead the return statement has wrong number of execution in gcov
Date: Sat, 19 Jan 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at nju dot edu.cn
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-83599-4-BC9evNx6WG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83599-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: 2019-01/txt/msg02651.txt.bz2
Content-length: 473

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

--- Comment #2 from Yibiao Yang <yangyibiao at nju dot edu.cn> ---
(In reply to Martin LiÅ¡ka from comment #1)
> Thanks for another report, in this case the code is invalid:
> 
>  gcc pr83599.c -Wreturn-type
> pr83599.c: In function â€˜funcâ€™:
> pr83599.c:7:1: warning: control reaches end of non-void function
> [-Wreturn-type]
>  }
>  ^

Thanks, Martin. Will avoid such kind of invalid bug report.
>From gcc-bugs-return-629843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 12:33:05 2019
Return-Path: <gcc-bugs-return-629843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126552 invoked by alias); 19 Jan 2019 12:33:05 -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 126481 invoked by uid 48); 19 Jan 2019 12:33:01 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88922] Merge identical constants with different modes
Date: Sat, 19 Jan 2019 12:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88922-4-ZBSIo3PGSr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88922-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: 2019-01/txt/msg02652.txt.bz2
Content-length: 794

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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-19
                 CC|                            |ebotcazou at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> gcc fails to notice that the 3 constants are the same. I would have expected
> the constant pool to be handled as an untyped collection of bits at the end.

That's indeed not the case, but I wonder if that would be worth the hassle.
>From gcc-bugs-return-629844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 13:23:41 2019
Return-Path: <gcc-bugs-return-629844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67973 invoked by alias); 19 Jan 2019 13:23:40 -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 67864 invoked by uid 48); 19 Jan 2019 13:23:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80265] __builtin_{memcmp,memchr,strlen} are not usable in constexpr functions
Date: Sat, 19 Jan 2019 13:23: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: 7.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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:
Message-ID: <bug-80265-4-FUvDHX9Mbh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80265-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80265-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: 2019-01/txt/msg02653.txt.bz2
Content-length: 963

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

--- Comment #36 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #35)
> I just noticed that Jonathan has already written such a patch in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86590#c28 but didn't commit it
> (maybe because is_constant_evaluated was not committed yet, or because it
> was not sufficient to solve that PR).

I think in the exact PR86590 case in the end __builtin_is_constant_evaluated()
hasn't helped, but it can in other cases; without it, the __builtin_constant_p
isn't folded at least in the most common case where the argument is not
constant early enough, it isn't folded during/after early inlining, nor soon
after IPA inlining, it is just fab pass.  While with
__builtin_is_constant_evaluated(), it can be optimized either before early
inlining (if it is used directly in the function), or soon after early inlining
(otherwise).
>From gcc-bugs-return-629845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 14:27:05 2019
Return-Path: <gcc-bugs-return-629845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60348 invoked by alias); 19 Jan 2019 14:27: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 60227 invoked by uid 48); 19 Jan 2019 14:27:00 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32628] [4.3 Regression] bogus integer overflow warning
Date: Sat, 19 Jan 2019 14:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.3.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-32628-4-TmGgTevbV0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32628-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32628-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: 2019-01/txt/msg02654.txt.bz2
Content-length: 367

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

--- Comment #12 from Marc Glisse <glisse at gcc dot gnu.org> ---
Nowadays, we consider that we can only access half of the address space, and
you can only add up to PTRDIFF_MAX to a pointer, so in some sense this does
overflow. I am thinking of removing the testcase, which breaks with a patch I
am working on.
>From gcc-bugs-return-629846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 15:58:13 2019
Return-Path: <gcc-bugs-return-629846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64587 invoked by alias); 19 Jan 2019 15:58:13 -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 64519 invoked by uid 48); 19 Jan 2019 15:58:08 -0000
From: "yangyibiao at nju dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88924] New: [GCOV] Wrong frequencies when there is complicated if expressions in gcov
Date: Sat, 19 Jan 2019 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at nju dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88924-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: 2019-01/txt/msg02655.txt.bz2
Content-length: 3597

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

            Bug ID: 88924
           Summary: [GCOV] Wrong frequencies when there is complicated if
                    expressions in gcov
           Product: gcc
           Version: 7.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: yangyibiao at nju dot edu.cn
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.3.0-27ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)

$ cat small.c
int ca[6] = {244, -245, 244, -246, 245, -246};

void main()
{
  for (int i = 0; i < 6; ++i) {
    int flag = i % 2 == 1 && ca[i] != (-2 * i - 1955) >> 3;
    if (flag) {
      ;
    } else if (i % 2 == 0 && ca[i] != (1955 + 2 * i) >> 3) {
      ;
    }
  }

  for (int i = 0; i < 6; ++i) {
    if (i % 2 == 1 && ca[i] != (-2 * i - 1955) >> 3) {
      ;
    } else if (i % 2 == 0 && ca[i] != (1955 + 2 * i) >> 3) {
      ;
    }
  }
}


$ gcc small.c -w --coverage; ./a.out; gcov small.c; cat small.c.gcov
File 'small.c'
Lines executed:100.00% of 9
Creating 'small.c.gcov'

        -:    0:Source:small.c
        -:    0:Graph:small.gcno
        -:    0:Data:small.gcda
        -:    0:Runs:1
        -:    0:Programs:1
        -:    1:int ca[6] = {244, -245, 244, -246, 245, -246};
        -:    2:
        1:    3:void main()
        -:    4:{
        7:    5:  for (int i = 0; i < 6; ++i) {
        6:    6:    int flag = i % 2 == 1 && ca[i] != (-2 * i - 1955) >> 3;
        6:    7:    if (flag) {
        -:    8:      ;
        6:    9:    } else if (i % 2 == 0 && ca[i] != (1955 + 2 * i) >> 3) {
        -:   10:      ;
        -:   11:    }
        -:   12:  }
        -:   13:
        7:   14:  for (int i = 0; i < 6; ++i) {
        6:   15:    if (i % 2 == 1 && ca[i] != (-2 * i - 1955) >> 3) {
        -:   16:      ;
        3:   17:    } else if (i % 2 == 0 && ca[i] != (1955 + 2 * i) >> 3) {
        -:   18:      ;
        -:   19:    }
        -:   20:  }
        1:   21:}
        -:   22:


Line #17 is wrongly marked as executed 3 times. In fact, this line should be
executed 6 times same to Line #9.
>From gcc-bugs-return-629847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 17:18:02 2019
Return-Path: <gcc-bugs-return-629847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112156 invoked by alias); 19 Jan 2019 17:18:02 -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 110654 invoked by uid 48); 19 Jan 2019 17:17:58 -0000
From: "ssbssa at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88925] New: address of static string changes
Date: Sat, 19 Jan 2019 17:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ssbssa at yahoo dot de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-88925-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: 2019-01/txt/msg02656.txt.bz2
Content-length: 1234

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

            Bug ID: 88925
           Summary: address of static string changes
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ssbssa at yahoo dot de
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Created attachment 45468
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45468&action=edit
test case

With the attached file, I get an unexpected result with these arguments:
$ g++ -ovirtual virtual.cpp -flto -flto-partition=max -O3

$ ./virtual

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


This is a heavily reduced test case of another program of mine, but I didn't
need -flto-partition=max there to get this problem (I think because it's a lot
bigger).

So the problem is with the static strings typeDerived1 and typeDerived2.
I would expect the pointers of Derived1::getType() and Derived2::getType() to
always match either typeDerived1 or typeDerived2.
>From gcc-bugs-return-629848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 20:07:18 2019
Return-Path: <gcc-bugs-return-629848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1852 invoked by alias); 19 Jan 2019 20:07:18 -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 1770 invoked by uid 55); 19 Jan 2019 20:07:14 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56789] Handling of contiguous dummy arguments
Date: Sat, 19 Jan 2019 20:07: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.9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-56789-4-pRXKlQVDRF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56789-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: 2019-01/txt/msg02657.txt.bz2
Content-length: 1048

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

--- Comment #23 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sat Jan 19 20:06:41 2019
New Revision: 268096

URL: https://gcc.gnu.org/viewcvs?rev=268096&root=gcc&view=rev
Log:
2018-01-19  Thomas Koenig  <tkoenig@gcc.gnu.org>
        Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/56789
        * trans-expr.c (gfc_conv_procedure_call): Call
        gfc_conv_subref_array_arg if the formal arg is contiguous
        and the actual arg may not be.

2018-01-19  Thomas Koenig  <tkoenig@gcc.gnu.org>
        Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/56789
        * gfortran.dg/contiguous_3.f90: Make code compilant.  Remove
        scan-tree tests that fail with patch.
        * gfortran.dg/contiguous_8.f90: New test.


Added:
    trunk/gcc/testsuite/gfortran.dg/contiguous_8.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/contiguous_3.f90
>From gcc-bugs-return-629849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 20:08:41 2019
Return-Path: <gcc-bugs-return-629849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3222 invoked by alias); 19 Jan 2019 20:08:41 -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 3104 invoked by uid 48); 19 Jan 2019 20:08:36 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56789] Handling of contiguous dummy arguments
Date: Sat, 19 Jan 2019 20:08: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.9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-56789-4-V4khCJGug8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56789-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: 2019-01/txt/msg02658.txt.bz2
Content-length: 446

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #24 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk, closing.
>From gcc-bugs-return-629850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:19:04 2019
Return-Path: <gcc-bugs-return-629850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51777 invoked by alias); 19 Jan 2019 21:19: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 51653 invoked by uid 55); 19 Jan 2019 21:18:58 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77960] ICE in gfc_conv_ss_startstride, at fortran/trans-array.c:3966
Date: Sat, 19 Jan 2019 21:19: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: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77960-4-YhKME05hxc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77960-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: 2019-01/txt/msg02659.txt.bz2
Content-length: 678

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

--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sat Jan 19 21:18:26 2019
New Revision: 268097

URL: https://gcc.gnu.org/viewcvs?rev=268097&root=gcc&view=rev
Log:
2019-01-19  Steven G. Kargl  <kargl@gcc.gnu.org>

        PR fortran/77960
        * io.c (match_io_element): input-item cannot be an external function.

2019-01-19  Steven G. Kargl  <kargl@gcc.gnu.org>

        PR fortran/77960
        * gfortran.dg/pr77960.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/pr77960.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/io.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:21:30 2019
Return-Path: <gcc-bugs-return-629851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54368 invoked by alias); 19 Jan 2019 21:21:30 -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 54302 invoked by uid 48); 19 Jan 2019 21:21:26 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77960] ICE in gfc_conv_ss_startstride, at fortran/trans-array.c:3966
Date: Sat, 19 Jan 2019 21:21: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: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-77960-4-uzN6MKrOvE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77960-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: 2019-01/txt/msg02660.txt.bz2
Content-length: 409

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from kargl at gcc dot gnu.org ---
Fixed on trunk. Closing.
>From gcc-bugs-return-629852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:23:11 2019
Return-Path: <gcc-bugs-return-629852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56495 invoked by alias); 19 Jan 2019 21:23:11 -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 56364 invoked by uid 48); 19 Jan 2019 21:23:07 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24878] subroutine getting called illegally as a function
Date: Sat, 19 Jan 2019 21:23: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.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-24878-4-ivtQMRGyea@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-24878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-24878-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: 2019-01/txt/msg02661.txt.bz2
Content-length: 481

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #5 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
This is not caught by ifort or PGI fortran either. Nagfor, however, gets it.
>From gcc-bugs-return-629853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:30:02 2019
Return-Path: <gcc-bugs-return-629853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64171 invoked by alias); 19 Jan 2019 21:30:01 -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 64052 invoked by uid 48); 19 Jan 2019 21:29:55 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25095] Disallowed intrinsic in initialization statement
Date: Sat, 19 Jan 2019 21:30: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.1.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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:
Message-ID: <bug-25095-4-VYOfEge74e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-25095-4@http.gcc.gnu.org/bugzilla/>
References: <bug-25095-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: 2019-01/txt/msg02662.txt.bz2
Content-length: 249

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

--- Comment #7 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Indeed, ifort and PGI fortran flag this as an error in the implied DO
expression. Nagfor flags it just as an extension.
>From gcc-bugs-return-629854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:36:17 2019
Return-Path: <gcc-bugs-return-629854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82491 invoked by alias); 19 Jan 2019 21:36:17 -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 78692 invoked by uid 48); 19 Jan 2019 21:36:08 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25714] concat of strings create an extra temporary variable
Date: Sat, 19 Jan 2019 21:36: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.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-25714-4-QkVZ0jlMLD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-25714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-25714-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: 2019-01/txt/msg02663.txt.bz2
Content-length: 574

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #7 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
This seems to be now
           _gfortran_concat_string (2, &str.0, 1, &a, 1, &b);
            __builtin_memmove (&c, &str.0, 2);
so it still has a temporary AFAIC tell.
>From gcc-bugs-return-629855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:46:33 2019
Return-Path: <gcc-bugs-return-629855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103333 invoked by alias); 19 Jan 2019 21:46:33 -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 103242 invoked by uid 55); 19 Jan 2019 21:46:28 -0000
From: "dominiq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37835] -fno-automatic does not work for derived types with default initalizer
Date: Sat, 19 Jan 2019 21:46: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.4.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq 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:
Message-ID: <bug-37835-4-yD8HXGqaQl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37835-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: 2019-01/txt/msg02664.txt.bz2
Content-length: 808

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

--- Comment #7 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sat Jan 19 21:45:43 2019
New Revision: 268098

URL: https://gcc.gnu.org/viewcvs?rev=268098&root=gcc&view=rev
Log:
2019-01-19  Dominique d'Humieres  <dominiq@gcc.gnu.org>

        PR fortran/37835
        * resolve.c (resolve_types): Add !flag_automatic.
        * symbol.c (gfc_add_save): Silence warnings.

2019-01-18  Dominique d'Humieres  <dominiq@gcc.gnu.org>

        PR fortran/37835
        * gfortran.dg/no-automatic.f90: New test.


Added:
    trunk/gcc/testsuite/gfortran.dg/no-automatic.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/invoke.texi
    trunk/gcc/fortran/resolve.c
    trunk/gcc/fortran/symbol.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 19 21:50:27 2019
Return-Path: <gcc-bugs-return-629856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113789 invoked by alias); 19 Jan 2019 21:50:27 -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 113676 invoked by uid 48); 19 Jan 2019 21:50:23 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37835] -fno-automatic does not work for derived types with default initalizer
Date: Sat, 19 Jan 2019 21:50: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.4.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-37835-4-251XaeTmOF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37835-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: 2019-01/txt/msg02665.txt.bz2
Content-length: 441

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Closing.
>From gcc-bugs-return-629857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 00:23:45 2019
Return-Path: <gcc-bugs-return-629857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51498 invoked by alias); 20 Jan 2019 00:23:45 -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 51419 invoked by uid 48); 20 Jan 2019 00:23:39 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86167] allocation variable length character array in derived type incorrect
Date: Sun, 20 Jan 2019 00:23: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86167-4-pgQcLOQqsm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86167-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86167-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: 2019-01/txt/msg02666.txt.bz2
Content-length: 191

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

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This seems to have been fixed on trunk (9.0) around 2018-09-26.
>From gcc-bugs-return-629858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 01:13:01 2019
Return-Path: <gcc-bugs-return-629858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76364 invoked by alias); 20 Jan 2019 01:13:01 -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 76268 invoked by uid 48); 20 Jan 2019 01:12:56 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/78685] -Og generates too many "<optimized out>"s
Date: Sun, 20 Jan 2019 01:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager 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:
Message-ID: <bug-78685-4-LNnkBOgRAE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78685-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: 2019-01/txt/msg02667.txt.bz2
Content-length: 864

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

--- Comment #15 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #13)
> (In reply to Tom de Vries from comment #12)
> > Created attachment 44343 [details]
> 
> > [debug] Add fkeep-vars-live
> 
> > Guality testing status: Og -fkeep-vars-live gives better results than Og for
> > pr54200.c and pr54970.c, but worse results here:
> > ...
> > FAIL: gcc.dg/guality/csttest.c  -Og -fkeep-vars-live -DPREVENT_OPTIMIZATION  \
> >       line 29 n == -(0x17ULL << 50)
> > FAIL: gcc.dg/guality/csttest.c  -Og -fkeep-vars-live -DPREVENT_OPTIMIZATION  \
> >       line 55 j == -(0x17ULL << 31)
> > ...
> 
> Looks like an independent problem, filed as PR86455 - "var-tracking
> mishandles pre_dec".

That's been fixed now... time to give this one another try?
>From gcc-bugs-return-629859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 01:16:14 2019
Return-Path: <gcc-bugs-return-629859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79694 invoked by alias); 20 Jan 2019 01:16:13 -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 79346 invoked by uid 48); 20 Jan 2019 01:16:06 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88926] New: ivopts with some NOP conversions
Date: Sun, 20 Jan 2019 01:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88926-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: 2019-01/txt/msg02668.txt.bz2
Content-length: 1582

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

            Bug ID: 88926
           Summary: ivopts with some NOP conversions
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: glisse at gcc dot gnu.org
  Target Milestone: ---

Starting from gcc.dg/tree-ssa/ivopts-lt-2.c:

/* { dg-do compile } */
/* { dg-options "-O2 -fdump-tree-ivopts" } */
/* { dg-skip-if "PR68644" { hppa*-*-* powerpc*-*-* } } */

void
f1 (int *p, unsigned int i)
{
  p += i;
  do
    {
      *p = 0;
      p += 1;
      i++;
    }
  while (i < 100);
}

/* { dg-final { scan-tree-dump-times "PHI" 1 "ivopts" } } */
/* { dg-final { scan-tree-dump-times "PHI <p_" 1 "ivopts"} } */
/* { dg-final { scan-tree-dump-times "p_\[0-9\]* <" 1 "ivopts" } } */

ivopts normally manages to get rid of i in the loop. However, if I replace "p
+= i" with

  __PTRDIFF_TYPE__ o = i;
  o *= 4;
  p = (char*)p + o;

(i.e. I compute i*4 in type 'long' instead of 'unsigned long')
ivopts doesn't find an invariant and doesn't eliminate i anymore.

This will be useful if I try to resurrect
https://gcc.gnu.org/ml/gcc-patches/2017-05/msg01641.html . I am not familiar
with ivopts (I don't see why the instruction p+=i is relevant, it only changes
the initial value of p, but without it we do not eliminate either) so this is
likely one of the last cases I'll try to fix.
>From gcc-bugs-return-629860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 05:35:09 2019
Return-Path: <gcc-bugs-return-629860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107367 invoked by alias); 20 Jan 2019 05:35:09 -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 107275 invoked by uid 48); 20 Jan 2019 05:35:04 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38182] stddef.h assumes machinee/ansi.h defines _ANSI_H_
Date: Sun, 20 Jan 2019 05:35: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: 4.4.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-38182-4-L8rFjQwUHJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38182-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38182-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: 2019-01/txt/msg02669.txt.bz2
Content-length: 874

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

--- Comment #18 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #16)
> Subject: Re:  stddef.h assumes machinee/ansi.h defines
>  _ANSI_H_
> 
> On Mon, 7 Sep 2009, prlw1 at cam dot ac dot uk wrote:
> 
> > I just got stuck with this again: wondered why a NetBSD-5.99.15/i386 box with
> > gcc-HEAD wouldn't compile. Then remembered the #define _ANSI_H_ fix and all is
> > well. What is impeding this patch from being applied?
> 
> I don't recall seeing weekly pings of it; presumably no maintainer in a 
> relevant area picked up review of it the first and only time it was posted 
> and noone made maintainers aware of the continued need for review by 
> pinging it until it gets reviewed.

There been any new pings in the last 9 and a half years?
>From gcc-bugs-return-629861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 05:37:05 2019
Return-Path: <gcc-bugs-return-629861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108978 invoked by alias); 20 Jan 2019 05:37: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 108937 invoked by uid 48); 20 Jan 2019 05:37:00 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/51450] configure's test for -fno-rtti -fno-exceptions broken
Date: Sun, 20 Jan 2019 05:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager 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:
Message-ID: <bug-51450-4-XjJSWp1Svw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51450-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: 2019-01/txt/msg02670.txt.bz2
Content-length: 207

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

--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
Is this an issue with upstream libtool, too, or just GCC's patched version of
it?
>From gcc-bugs-return-629862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 05:38:43 2019
Return-Path: <gcc-bugs-return-629862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110853 invoked by alias); 20 Jan 2019 05:38:43 -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 110745 invoked by uid 48); 20 Jan 2019 05:38:37 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjLzQxMDQ1XSBFeHRlbmRlZCBhc20gd2l0aCBDIG9wZXJhbmRzIGRv?= =?UTF-8?B?ZXNu4oCZdCB3b3JrIGF0IHRvcCBsZXZlbA==?Date: Sun, 20 Jan 2019 05:38: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-41045-4-sn4gpw4ZSe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41045-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41045-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: 2019-01/txt/msg02671.txt.bz2
Content-length: 354

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

--- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Steven Fuerst from comment #9)
> 
> Of course... since this is not exactly the intent of the (section())
> attribute, tricks like this may break at any time.

"not exactly the intent" is a bit of an understatement!
>From gcc-bugs-return-629863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 06:13:32 2019
Return-Path: <gcc-bugs-return-629863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61731 invoked by alias); 20 Jan 2019 06:13:32 -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 61651 invoked by uid 48); 20 Jan 2019 06:13:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] New: [9 Regression] Bootstrap failure on arm in libgo
Date: Sun, 20 Jan 2019 06:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
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 cc target_milestone
Message-ID: <bug-88927-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: 2019-01/txt/msg02672.txt.bz2
Content-length: 1410

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

            Bug ID: 88927
           Summary: [9 Regression] Bootstrap failure on arm in libgo
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: jakub at gcc dot gnu.org
                CC: cmang at google dot com
  Target Milestone: ---

../../../libgo/go/internal/cpu/cpu.go:138:2: error: reference to undefined name
'doinit'
  138 |  doinit()
      |  ^
make[4]: Leaving directory
'/builddir/build/BUILD/gcc-9.0.0-20190119/obj-armv7hl-redhat-linux-gnueabi/armv7hl-redhat-linux-gnueabi/libgo'
make[4]: *** [Makefile:2833: internal/cpu.lo] Error 1
make[3]: *** [Makefile:2231: all-recursive] Error 1
make[3]: Leaving directory
'/builddir/build/BUILD/gcc-9.0.0-20190119/obj-armv7hl-redhat-linux-gnueabi/armv7hl-redhat-linux-gnueabi/libgo'
make[2]: Leaving directory
'/builddir/build/BUILD/gcc-9.0.0-20190119/obj-armv7hl-redhat-linux-gnueabi/armv7hl-redhat-linux-gnueabi/libgo'
make[2]: *** [Makefile:1156: all] Error 2
make[1]: *** [Makefile:20894: all-target-libgo] Error 2
make[1]: *** Waiting for unfinished jobs....

No idea why, there is cpu_no_init.go with
// +build !386
// +build !amd64
// +build !amd64p32
// +build !arm64
// +build !ppc64
// +build !ppc64le
// +build !s390x
>From gcc-bugs-return-629864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 06:16:20 2019
Return-Path: <gcc-bugs-return-629864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64597 invoked by alias); 20 Jan 2019 06:16:16 -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 63733 invoked by uid 48); 20 Jan 2019 06:15:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Sun, 20 Jan 2019 06:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget target_milestone short_desc
Message-ID: <bug-88927-4-9MhNbWYtGx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02673.txt.bz2
Content-length: 637

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |armv7hl-unknown-linux-gnuea
                   |                            |bi
   Target Milestone|---                         |9.0
            Summary|[9 Regression] Bootstrap    |[9 Regression] Bootstrap
                   |failure on arm in libgo     |failure on arm in libgo
                   |                            |starting with r268084
>From gcc-bugs-return-629865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 06:44:45 2019
Return-Path: <gcc-bugs-return-629865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88572 invoked by alias); 20 Jan 2019 06:44:45 -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 88507 invoked by uid 48); 20 Jan 2019 06:44:41 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Sun, 20 Jan 2019 06:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88927-4-iBC7HKESvL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02674.txt.bz2
Content-length: 171

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

--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
This is likely fixed by https://golang.org/cl/158717.
>From gcc-bugs-return-629866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 07:05:04 2019
Return-Path: <gcc-bugs-return-629866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104887 invoked by alias); 20 Jan 2019 07:05: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 104792 invoked by uid 48); 20 Jan 2019 07:04:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Sun, 20 Jan 2019 07:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88927-4-FQjbVMgoLd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02675.txt.bz2
Content-length: 1144

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Will try that.  That said, I don't understand why cpu_no_init.go isn't used in
that case.
Inthe build log I see
/usr/bin/mkdir -p internal; files=`echo ../../../libgo/go/internal/cpu/cpu.go
cpugen.go | sed -e 's/[^ ]*\.gox//g' -e 's/[^ ]*\.dep//'`; /bin/sh ./libtool
--tag GO --mode=compile
/builddir/build/BUILD/gcc-9.0.0-20190119/obj-armv7hl-redhat-linux-gnueabi/./gcc/gccgo
-B/builddir/build/BUILD/gcc-9.0.0-20190119/obj-armv7hl-redhat-linux-gnueabi/./gcc/
-B/usr/armv7hl-redhat-linux-gnueabi/bin/
-B/usr/armv7hl-redhat-linux-gnueabi/lib/ -isystem
/usr/armv7hl-redhat-linux-gnueabi/include -isystem
/usr/armv7hl-redhat-linux-gnueabi/sys-include       -O2 -g -I . -c
-fgo-pkgpath=`echo internal/cpu.lo | sed -e 's/.lo$//'`  -o internal/cpu.lo
$files
but if I run by hand (on x86_64-linux):
../../../libgo/match.sh --goarch=arm --goos=linux
--srcdir=../../../libgo/go/internal/cpu --extrafiles="cpugen.go"
../../../libgo/go/internal/cpu/cpu.go
../../../libgo/go/internal/cpu/cpu_no_init.go cpugen.go
>From gcc-bugs-return-629867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 08:33:33 2019
Return-Path: <gcc-bugs-return-629867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79140 invoked by alias); 20 Jan 2019 08:33:33 -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 79060 invoked by uid 48); 20 Jan 2019 08:33:27 -0000
From: "belyshev at depni dot sinp.msu.ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] New: [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Sun, 20 Jan 2019 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: belyshev at depni dot sinp.msu.ru
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88928-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: 2019-01/txt/msg02676.txt.bz2
Content-length: 1644

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

            Bug ID: 88928
           Summary: [9 Regression] ICE segfault in
                    check_address_or_pointer_of_packed_member since
                    r268075
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: belyshev at depni dot sinp.msu.ru
                CC: hjl.tools at gmail dot com
  Target Milestone: ---

// bug.c
struct a { } __attribute__((__packed__));
void c (struct a **);
void d (const struct a *b) { c ((struct a **) b); }


$ ./cc1 -quiet bug.c 
bug.c: In function 'd':
bug.c:3:41: warning: converting a packed 'const struct a *' pointer (alignment
1) to 'struct a *' (alignment 8) may result in an unaligned pointer value
[-Waddress-of-packed-member]
    3 | void d (const struct a *b) { c ((struct a **) b); }
      |                                         ^
bug.c:3:41: internal compiler error: Segmentation fault
0x1120e22 crash_signal
        ../../gcc/gcc/toplev.c:326
0x7f35308e88df ???
       
/build/glibc-T8GPG6/glibc-2.28/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x81a107 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
        ../../gcc/gcc/tree.h:3289
0x993f6f check_address_or_pointer_of_packed_member
        ../../gcc/gcc/c-family/c-warn.c:2762
0x9941e4 check_and_warn_address_or_pointer_of_packed_member
        ../../gcc/gcc/c-family/c-warn.c:2838
...
>From gcc-bugs-return-629868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 08:43:22 2019
Return-Path: <gcc-bugs-return-629868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126208 invoked by alias); 20 Jan 2019 08:43:22 -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 126151 invoked by uid 48); 20 Jan 2019 08:43:17 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] New: ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Sun, 20 Jan 2019 08:43: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault 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 target_milestone
Message-ID: <bug-88929-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: 2019-01/txt/msg02677.txt.bz2
Content-length: 3886

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

            Bug ID: 88929
           Summary: ICE on building MPICH 3.2 with GCC 9 with
                    ISO_Fortran_binding
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: pault at gcc dot gnu.org
          Reporter: pault at gcc dot gnu.org
  Target Milestone: ---

Reported by Damian ROuson.

During the MPICH3.2 build:

  FC       src/binding/fortran/use_mpi_f08/wrappers_f/add_error_class_f08ts.lo
/home/rouson/Builds/opencoarrays/prerequisites/downloads/mpich-3.2/src/binding/fortran/use_mpi_f08/wrappers_f/accumulate_f08ts.f90:39:0:

   39 |             target_disp, target_count,
target_datatype%MPI_VAL, op%MPI_VAL, win%MPI_VAL)
      |
internal compiler error: tree check: expected tree that contains â€˜decl
commonâ€™ structure, have â€˜indirect_refâ€™ in
gfc_conv_gfc_desc_to_cfi_desc, at fortran/trans-expr.c:4927
  FC       src/binding/fortran/use_mpi_f08/wrappers_f/add_error_code_f08ts.lo
0x605269 tree_contains_struct_check_failed(tree_node const*,
tree_node_structure_enum, char const*, int, char const*)
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/tree.c:9983
0x75bf29 contains_struct_check(tree_node*, tree_node_structure_enum,
char const*, int, char const*)
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/tree.h:3290
0x75bf29 gfc_conv_gfc_desc_to_cfi_desc
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-expr.c:4927
0x755c92 gfc_conv_procedure_call(gfc_se*, gfc_symbol*,
gfc_actual_arglist*, gfc_expr*, vec<tree_node*, va_gc, vl_embed>*)
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-expr.c:5785
0x758d5a gfc_conv_expr(gfc_se*, gfc_expr*)
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-expr.c:8228
0x763dc1 gfc_trans_assignment_1
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-expr.c:10437
0x712047 trans_code
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans.c:1822
0x7a0d83 gfc_trans_if_1
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-stmt.c:1448
0x7aac5a gfc_trans_if(gfc_code*)
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-stmt.c:1479
0x711ea7 trans_code
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans.c:1910
0x74868d gfc_generate_function_code(gfc_namespace*)
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/trans-decl.c:6526
0x6c29a6 translate_all_program_units
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/parse.c:6134
0x6c29a6 gfc_parse_file()
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/parse.c:6337
0x70e10f gfc_be_parse_file
/home/rouson/Builds/opencoarrays/prerequisites/downloads/trunk/gcc/fortran/f95-lang.c:204
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
make[2]: *** [src/binding/fortran/use_mpi_f08/wrappers_f/accumulate_f08ts.lo]
Error 1
Makefile:38450: recipe for target
'src/binding/fortran/use_mpi_f08/wrappers_f/accumulate_f08ts.lo'
failed
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
'/home/rouson/Desktop/Builds/opencoarrays/prerequisites/builds/mpich-3.2'
make[1]: *** [all-recursive] Error 1
Makefile:38662: recipe for target 'all-recursive' failed
make[1]: Leaving directory
'/home/rouson/Desktop/Builds/opencoarrays/prerequisites/builds/mpich-3.2'
make: *** [all] Error 2
Makefile:10307: recipe for target 'all' failed
>From gcc-bugs-return-629869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 08:46:12 2019
Return-Path: <gcc-bugs-return-629869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129618 invoked by alias); 20 Jan 2019 08:46:11 -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 129467 invoked by uid 48); 20 Jan 2019 08:46:07 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Sun, 20 Jan 2019 08:46: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88929-4-ZSyuOdIYPt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg02678.txt.bz2
Content-length: 388

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

--- Comment #1 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 45469
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45469&action=edit
A proposed patch for the PR.

Handling of fortran dummy arguments was not implemented in the recent
ISO_Fortran_binding patch. The attached rectifies that omission.

Paul
>From gcc-bugs-return-629870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 08:47:04 2019
Return-Path: <gcc-bugs-return-629870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130599 invoked by alias); 20 Jan 2019 08:47:03 -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 130536 invoked by uid 48); 20 Jan 2019 08:47:00 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Sun, 20 Jan 2019 08:47: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88929-4-HiGydPxaQK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg02679.txt.bz2
Content-length: 536

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

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-20
                 CC|                            |damian at sourceryinstitute dot or
                   |                            |g
     Ever confirmed|0                           |1
>From gcc-bugs-return-629872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 08:54:49 2019
Return-Path: <gcc-bugs-return-629872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7331 invoked by alias); 20 Jan 2019 08:54:48 -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 7290 invoked by uid 48); 20 Jan 2019 08:54:44 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzg4OTA4XSBbOSBSZWdyZXNzaW9uXSBJQ0UgaW4gdHJl?= =?UTF-8?B?ZSBjaGVjazogZXhwZWN0ZWQgdHJlZSB0aGF0IGNvbnRhaW5zIOKAmGRlY2wg?= =?UTF-8?B?Y29tbW9u4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpbmRpcmVjdF9yZWbigJkg?= =?UTF-8?B?aW4gZ2ZjX2NvbnZfZ2ZjX2Rlc2NfdG9fY2ZpX2Rlc2MsIGF0IGZvcnRyYW4v?= =?UTF-8?B?dHJhbnMtZXhwci5jOjQ5Mjc=?Date: Sun, 20 Jan 2019 08:54: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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:
Message-ID: <bug-88908-4-H3ALJHFx88@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88908-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88908-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: 2019-01/txt/msg02681.txt.bz2
Content-length: 199

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

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This looks like a duplicate of pr88929 where a patch has been proposed.
>From gcc-bugs-return-629871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 08:54:03 2019
Return-Path: <gcc-bugs-return-629871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6318 invoked by alias); 20 Jan 2019 08:54:02 -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 6247 invoked by uid 48); 20 Jan 2019 08:53:58 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Sun, 20 Jan 2019 08:54: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88929-4-7aXYCKXNWd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg02680.txt.bz2
Content-length: 433

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pault at gcc dot gnu.org

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This looks like a duplicate of pr88908.
>From gcc-bugs-return-629873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 10:35:21 2019
Return-Path: <gcc-bugs-return-629873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61484 invoked by alias); 20 Jan 2019 10:35: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 61427 invoked by uid 48); 20 Jan 2019 10:35:16 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30123] Document INQUIRE, especially UNFORMATTED and FORMATTED
Date: Sun, 20 Jan 2019 10:35: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.3.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-30123-4-C0wgMrTIlb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30123-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30123-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: 2019-01/txt/msg02682.txt.bz2
Content-length: 524

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #4 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
This seems like one of these documentation tasks which is in principle very
easy to do but nobody is motivated to do.^^
>From gcc-bugs-return-629875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 10:38:21 2019
Return-Path: <gcc-bugs-return-629875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63789 invoked by alias); 20 Jan 2019 10:38: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 63719 invoked by uid 48); 20 Jan 2019 10:38:17 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Sun, 20 Jan 2019 10:38: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88929-4-d12bB2CI1t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg02684.txt.bz2
Content-length: 456

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 88908 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-629874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 10:38:21 2019
Return-Path: <gcc-bugs-return-629874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63780 invoked by alias); 20 Jan 2019 10:38: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 63698 invoked by uid 48); 20 Jan 2019 10:38:17 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzg4OTA4XSBbOSBSZWdyZXNzaW9uXSBJQ0UgaW4gdHJl?= =?UTF-8?B?ZSBjaGVjazogZXhwZWN0ZWQgdHJlZSB0aGF0IGNvbnRhaW5zIOKAmGRlY2wg?= =?UTF-8?B?Y29tbW9u4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpbmRpcmVjdF9yZWbigJkg?= =?UTF-8?B?aW4gZ2ZjX2NvbnZfZ2ZjX2Rlc2NfdG9fY2ZpX2Rlc2MsIGF0IGZvcnRyYW4v?= =?UTF-8?B?dHJhbnMtZXhwci5jOjQ5Mjc=?Date: Sun, 20 Jan 2019 10:38: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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_status resolution
Message-ID: <bug-88908-4-vjt9e6KPUC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88908-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88908-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: 2019-01/txt/msg02683.txt.bz2
Content-length: 563

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The ICE is fixed by the patch for pr88929. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 88929 ***
>From gcc-bugs-return-629876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 10:41:51 2019
Return-Path: <gcc-bugs-return-629876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69185 invoked by alias); 20 Jan 2019 10:41:51 -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 69121 invoked by uid 48); 20 Jan 2019 10:41:47 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Sun, 20 Jan 2019 10:41: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88929-4-rTbc6FPrup@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg02685.txt.bz2
Content-length: 199

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

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
There is a partially reduced test in pr88908 (TODO reduce the modules).
>From gcc-bugs-return-629877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 11:01:19 2019
Return-Path: <gcc-bugs-return-629877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105639 invoked by alias); 20 Jan 2019 11:01:07 -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 105134 invoked by uid 48); 20 Jan 2019 11:00:33 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30438] Set but never used variable should raise warning
Date: Sun, 20 Jan 2019 11:01: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.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-30438-4-v9QEPNhxS3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30438-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: 2019-01/txt/msg02686.txt.bz2
Content-length: 462

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #10 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
nagfor does this warning, ifort and PGI fortran doesn't.
>From gcc-bugs-return-629878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 11:17:58 2019
Return-Path: <gcc-bugs-return-629878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49733 invoked by alias); 20 Jan 2019 11:17:58 -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 49699 invoked by uid 48); 20 Jan 2019 11:17:54 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30733] VOLATILE: Missed optimization - attribute not restricted to scope
Date: Sun, 20 Jan 2019 11:17: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.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-30733-4-AlHTWfeUlX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30733-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: 2019-01/txt/msg02687.txt.bz2
Content-length: 541

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #3 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
There were some changes with the optimization and the volatile attribute with
release 7.0. Maybe check if this issue is still present?
>From gcc-bugs-return-629879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 11:31:06 2019
Return-Path: <gcc-bugs-return-629879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63563 invoked by alias); 20 Jan 2019 11:31:05 -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 63470 invoked by uid 48); 20 Jan 2019 11:31:00 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31009] Generate conditional code to assign arrays, depending on their stride
Date: Sun, 20 Jan 2019 11:31: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.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-31009-4-W1bPczGPr7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-31009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-31009-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: 2019-01/txt/msg02688.txt.bz2
Content-length: 277

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

--- Comment #7 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Seems also to me that this should be reconsidered whether there is still need
for optimization for the case of arrays not declared as contiguous.
>From gcc-bugs-return-629880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 11:42:45 2019
Return-Path: <gcc-bugs-return-629880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69497 invoked by alias); 20 Jan 2019 11:42:45 -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 69443 invoked by uid 48); 20 Jan 2019 11:42:40 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88501] Improve suggested alternative to be closer to typo
Date: Sun, 20 Jan 2019 11:42: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: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88501-4-WZ14Mq4GN8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88501-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88501-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: 2019-01/txt/msg02689.txt.bz2
Content-length: 1230

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

--- Comment #7 from Jonny Grant <jg at jguk dot org> ---
Here is anotehr example.

I expected <string.h> to be suggested, as that contains exact match strerror()


Current G++ trunk output

<source>: In function 'int main()':

<source>:14:33: error: 'errno' was not declared in this scope

   14 |         printf("%s\n", strerror(errno));

      |                                 ^~~~~

<source>:4:1: note: 'errno' is defined in header '<cerrno>'; did you forget to
'#include <cerrno>'?

    3 | #include <stdio.h>

  +++ |+#include <cerrno>

    4 | int main()

<source>:14:24: error: 'strerror' was not declared in this scope; did you mean
'perror'?

   14 |         printf("%s\n", strerror(errno));

      |                        ^~~~~~~~

      |                        perror

Compiler returned: 1




example
// gcc -o glibc_realpath glibc_realpath.c
#include <stdlib.h>
#include <stdio.h>
int main()
{
    const char * path = "/usr/bin/../include/myheader.h";

    //errno = 0;
    char * result = realpath(path, NULL);
    printf("result: [%s]\n", result);

    if(NULL == result)
    {
        printf("%s\n", strerror(errno));
    }

    return 0;
}
>From gcc-bugs-return-629881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 11:50:07 2019
Return-Path: <gcc-bugs-return-629881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75387 invoked by alias); 20 Jan 2019 11:50:07 -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 75268 invoked by uid 48); 20 Jan 2019 11:50:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Sun, 20 Jan 2019 11:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88927-4-Jb7ApaRLlu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02690.txt.bz2
Content-length: 330

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Oops, ignore the cpu_no_init.go related comments, I was looking at my trunk
checkout apparently before r268084, while the failed build was with that change
which added +build !arm in there.  That explains it.
>From gcc-bugs-return-629882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 12:51:55 2019
Return-Path: <gcc-bugs-return-629882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31364 invoked by alias); 20 Jan 2019 12:51:55 -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 31241 invoked by uid 48); 20 Jan 2019 12:51:51 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34740] -fbounds-check with TRANSFER misses out of bounds in array assignment
Date: Sun, 20 Jan 2019 12:51: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.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-34740-4-sQBZiaLHMx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34740-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: 2019-01/txt/msg02691.txt.bz2
Content-length: 467

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #2 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Still not caught in trunk. nagfor and ifort do catch this one.
>From gcc-bugs-return-629883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 14:41:53 2019
Return-Path: <gcc-bugs-return-629883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2513 invoked by alias); 20 Jan 2019 14:41:53 -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 2462 invoked by uid 48); 20 Jan 2019 14:41:49 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68546] passing non-contiguous associated array section garbles results
Date: Sun, 20 Jan 2019 14:41: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: 5.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-68546-4-vObJFjN56s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68546-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68546-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: 2019-01/txt/msg02692.txt.bz2
Content-length: 450

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed, presumably by r268096.
>From gcc-bugs-return-629884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 14:54:40 2019
Return-Path: <gcc-bugs-return-629884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43831 invoked by alias); 20 Jan 2019 14:54:40 -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 42315 invoked by uid 48); 20 Jan 2019 14:54:34 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82215] Feature request to better support two pass compiling with gfortran
Date: Sun, 20 Jan 2019 14:54: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: unknown
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-82215-4-hXPbUJ4E4e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82215-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: 2019-01/txt/msg02693.txt.bz2
Content-length: 441

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch

--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Patch can be found here:

https://gcc.gnu.org/ml/fortran/2019-01/msg00102.html
>From gcc-bugs-return-629885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 15:19:32 2019
Return-Path: <gcc-bugs-return-629885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121022 invoked by alias); 20 Jan 2019 15:19:31 -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 120925 invoked by uid 48); 20 Jan 2019 15:19:27 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65438] Unnecessary ptr check
Date: Sun, 20 Jan 2019 15:19: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: 5.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: minor
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: cesar at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-65438-4-DfWphPtqs8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65438-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: 2019-01/txt/msg02694.txt.bz2
Content-length: 517

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING
                 CC|                            |tkoenig at gcc dot gnu.org

--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Is this still valid?

If not, maybe we can unclutter the bug database a bit.
>From gcc-bugs-return-629886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 15:33:38 2019
Return-Path: <gcc-bugs-return-629886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21455 invoked by alias); 20 Jan 2019 15:33: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 21419 invoked by uid 48); 20 Jan 2019 15:33:33 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Sun, 20 Jan 2019 15:33: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-88928-4-iHCj6tqcBf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg02695.txt.bz2
Content-length: 900

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-20
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
We should warn:

---
struct a { int i; } __attribute__((__packed__));
void c (struct a **);
void d (const struct a *b) { c ((struct a **) b); }
--

But should we warn 

--
struct a { } __attribute__((__packed__));
void c (struct a **);
void d (const struct a *b) { c ((struct a **) b); }
--

in C? Since "struct a" is empty, can we ever generate unaligned access
to an empty structure?
>From gcc-bugs-return-629887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 15:39:03 2019
Return-Path: <gcc-bugs-return-629887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31533 invoked by alias); 20 Jan 2019 15:39:03 -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 31452 invoked by uid 48); 20 Jan 2019 15:38:59 -0000
From: "yangyibiao at nju dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88930] New: [GCOV] Wrong frequences when a if statement is after a  ?: statement in gcov
Date: Sun, 20 Jan 2019 15:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at nju dot edu.cn
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88930-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: 2019-01/txt/msg02696.txt.bz2
Content-length: 3211

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

            Bug ID: 88930
           Summary: [GCOV] Wrong frequences when a if statement is after a
                     ?: statement in gcov
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: yangyibiao at nju dot edu.cn
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-1ubuntu2~18.04' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-1ubuntu2~18.04)

$ cat small.c
void foo(long dx, long dy, int xi, int yi)
{
  int hints = 0;
  if (dy != 0 && (dx <= 1155)) {
    hints = dy > 0 ? 2 : 1;
    if (xi) {
      hints = 1;
    }
  } else if (dx != 0 && (dy <= 0)) {
    hints = 2;
  } else {
    hints = 3;
  }
}
void main()
{
  foo(0, 18481, 1, 0);
}

$ gcc --coverage small.c; ./a.out; gcov small.c; cat small.c.gcov
File 'small.c'
Lines executed:76.92% of 13
Creating 'small.c.gcov'

        -:    0:Source:small.c
        -:    0:Graph:small.gcno
        -:    0:Data:small.gcda
        -:    0:Runs:1
        -:    0:Programs:1
        1:    1:void foo(long dx, long dy, int xi, int yi)
        -:    2:{
        1:    3:  int hints = 0;
        1:    4:  if (dy != 0 && (dx <= 1155)) {
       1*:    5:    hints = dy > 0 ? 2 : 1;
        2:    6:    if (xi) {
        1:    7:      hints = 1;
        -:    8:    }
    #####:    9:  } else if (dx != 0 && (dy <= 0)) {
    #####:   10:    hints = 2;
        -:   11:  } else {
    #####:   12:    hints = 3;
        -:   13:  }
        1:   14:}
        1:   15:void main()
        -:   16:{
        1:   17:  foo(0, 18481, 1, 0);
        1:   18:}

Line #6 is wrongly marked as executed twice. However, the foo  function is call
only once and there is no loop in function foo.
>From gcc-bugs-return-629888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 16:07:29 2019
Return-Path: <gcc-bugs-return-629888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12017 invoked by alias); 20 Jan 2019 16:07:29 -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 11966 invoked by uid 48); 20 Jan 2019 16:07:24 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Sun, 20 Jan 2019 16:07: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88928-4-15mMfqkP9d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg02697.txt.bz2
Content-length: 1028

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

Bernd Edlinger <bernd.edlinger at hotmail dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernd.edlinger at hotmail dot de

--- Comment #2 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to H.J. Lu from comment #1)
> We should warn:
> 
> ---
> struct a { int i; } __attribute__((__packed__));
> void c (struct a **);
> void d (const struct a *b) { c ((struct a **) b); }
> --
> 
> But should we warn 
> 
> --
> struct a { } __attribute__((__packed__));
> void c (struct a **);
> void d (const struct a *b) { c ((struct a **) b); }
> --
> 
> in C? Since "struct a" is empty, can we ever generate unaligned access
> to an empty structure?

I think we should warn, because b is aligned(1)
and the code in question passes it to struct a **, which is aligned(8)
which can get an alignment trap.
>From gcc-bugs-return-629889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 17:11:56 2019
Return-Path: <gcc-bugs-return-629889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128063 invoked by alias); 20 Jan 2019 17:11:56 -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 127883 invoked by uid 48); 20 Jan 2019 17:11:43 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88931] New: Failed to convert int128 to float/double with roundþ_UPWARD/FE_TOWARDZERO
Date: Sun, 20 Jan 2019 17:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88931-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: 2019-01/txt/msg02698.txt.bz2
Content-length: 2875

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

            Bug ID: 88931
           Summary: Failed to convert int128 to float/double with
                    round=FE_UPWARD/FE_TOWARDZERO
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
  Target Milestone: ---

[hjl@gnu-cfl-1 float128-5]$ cat x.c
#include <fenv.h>
#include <stdio.h>
#include <quadmath.h>

#pragma STDC FENV_ACCESS ON
#define ROUNDING(r) { r, #r }

int
main (void)
{
  char buf[128];
  union
    {
      long long ll[2];
      __int128 q;
    } u = { 0xdLL, 0x8000000000000000LL };
  int i;
  struct
    {
      int r;
      const char *s;
    } round[] =
  {
    ROUNDING (FE_DOWNWARD),
    ROUNDING (FE_UPWARD),
    ROUNDING (FE_TOWARDZERO),
    ROUNDING (FE_TONEAREST)
  };
  for (i = 0; i < sizeof (round) / sizeof (round[0]); i++) {
    fesetround(round[i].r);
    float f = (float) u.q;
    double d = (double) u.q;
    __float128 q = (__float128) u.q;
    printf("fegetround=%d: %d, %s\n",
           fegetround(), round[i].r, round[i].s);
    printf("f=%f\t%x\n", f, *(int*)&f);
    printf("d=%lf\t%llx\n", d,  *(long long*)&d);
    quadmath_snprintf(buf, 128, "%Qf", 100, q);
    printf("q=%s\t%016llx%016llx\n",
           buf, *((long long *)&q + 1), *(long long *)&q);
  }
  return 0;
}
[hjl@gnu-cfl-1 float128-5]$ make
gcc -std=c99 -fno-strict-aliasing -g    -c -o x.o x.c
gcc -o x x.o -lm -lquadmath
./x
fegetround=1024: 1024, FE_DOWNWARD
f=-170141183460469231731687303715884105728.000000       ff000000
d=-170141183460469231731687303715884105728.000000       c7e0000000000000
q=-170141183460469231731687303715884105728.000000      
c07e0000000000000000000000000000
fegetround=2048: 2048, FE_UPWARD
f=-170141183460469231731687303715884105728.000000       ff000000
d=-170141183460469231731687303715884105728.000000       c7e0000000000000
q=-170141183460469231731687303715884089344.000000      
c07dffffffffffffffffffffffffffff
fegetround=3072: 3072, FE_TOWARDZERO
f=-170141183460469231731687303715884105728.000000       ff000000
d=-170141183460469231731687303715884105728.000000       c7e0000000000000
q=-170141183460469231731687303715884089344.000000      
c07dffffffffffffffffffffffffffff
fegetround=0: 0, FE_TONEAREST
f=-170141183460469231731687303715884105728.000000       ff000000
d=-170141183460469231731687303715884105728.000000       c7e0000000000000
q=-170141183460469231731687303715884105728.000000      
c07e0000000000000000000000000000
[hjl@gnu-cfl-1 float128-5]$ 

For FE_UPWARD and FE_TOWARDZERO, float should be feffffff and double
should be c7dfffffffffffff.
>From gcc-bugs-return-629890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 17:16:34 2019
Return-Path: <gcc-bugs-return-629890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11042 invoked by alias); 20 Jan 2019 17:16:33 -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 10131 invoked by uid 48); 20 Jan 2019 17:16:18 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88926] ivopts with some NOP conversions
Date: Sun, 20 Jan 2019 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88926-4-PzXwkv6lVA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88926-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: 2019-01/txt/msg02699.txt.bz2
Content-length: 955

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

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
With similar changes, I analyzed gcc.dg/vect/pr25413a.c (which we then fail to
vectorize). I expect the issue is similar. In scalar evolution, we get a
polynomial_chrec of type unsigned long wrapped in a NOP_EXPR of type long and
chrec_fold_multiply turns that into chrec_dont_know. It does print a few lines
of "Analyzing # of iterations of loop" but eventually "failed: evolution of
base is not affine". resolve_mixers has a promising comment above about not
caring about overflows, but it doesn't actually redo the analysis (the
recursion with analyze_scalar_evolution_1, interpret_gimple_assign,
interpret_rhs_expr, and most importantly the chrec_convert and
chrec_fold_multiply). Paradoxically, -fwrapv lets us vectorize... However,
-fwrapv does not help for the testcase in this PR, so maybe the 2 are different
after all.
>From gcc-bugs-return-629891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 17:54:18 2019
Return-Path: <gcc-bugs-return-629891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23823 invoked by alias); 20 Jan 2019 17:54:17 -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 23654 invoked by uid 48); 20 Jan 2019 17:54:05 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88821] Inline packing of non-contiguous arguments
Date: Sun, 20 Jan 2019 17:54: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88821-4-VrldYgaNDt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88821-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: 2019-01/txt/msg02700.txt.bz2
Content-length: 382

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |tkoenig at gcc dot gnu.org
>From gcc-bugs-return-629892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 18:02:36 2019
Return-Path: <gcc-bugs-return-629892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39624 invoked by alias); 20 Jan 2019 18:02:36 -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 39504 invoked by uid 48); 20 Jan 2019 18:02:23 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88501] Improve suggested alternative to be closer to typo
Date: Sun, 20 Jan 2019 18:02: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: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88501-4-USpBTGpKfb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88501-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88501-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: 2019-01/txt/msg02701.txt.bz2
Content-length: 442

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

--- Comment #8 from Jonny Grant <jg at jguk dot org> ---


Another example - would be good if it could suggest <stdbool.h>

$ gcc -o undef undef.c
undef.c: In function â€˜mainâ€™:
undef.c:4:5: error: unknown type name â€˜boolâ€™; did you mean â€˜_Boolâ€™?
     bool a;
     ^~~~
     _Bool




int main ()
{
    bool a;
    a = 98;
    return 0;
}
>From gcc-bugs-return-629893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 18:31:17 2019
Return-Path: <gcc-bugs-return-629893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73633 invoked by alias); 20 Jan 2019 18:31:17 -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 73435 invoked by uid 48); 20 Jan 2019 18:31:01 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88931] Failed to convert int128 to float/double with roundþ_UPWARD/FE_TOWARDZERO
Date: Sun, 20 Jan 2019 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88931-4-h18EZzxaVl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88931-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: 2019-01/txt/msg02702.txt.bz2
Content-length: 153

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
You also need -frounding-math .
>From gcc-bugs-return-629894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 18:41:43 2019
Return-Path: <gcc-bugs-return-629894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87514 invoked by alias); 20 Jan 2019 18:41:42 -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 87379 invoked by uid 48); 20 Jan 2019 18:41:30 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88931] Failed to convert int128 to float/double with roundþ_UPWARD/FE_TOWARDZERO
Date: Sun, 20 Jan 2019 18:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88931-4-b15MVxosgJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88931-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: 2019-01/txt/msg02703.txt.bz2
Content-length: 639

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

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> You also need -frounding-math.

     The default is '-fno-rounding-math'.

     This option is experimental and does not currently guarantee to
     disable all GCC optimizations that are affected by rounding mode.
     Future versions of GCC may provide finer control of this setting
     using C99's 'FENV_ACCESS' pragma.  This command-line option will be
     used to specify the default state for 'FENV_ACCESS'.

Should "#pragma STDC FENV_ACCESS ON" enable -frounding-math?
>From gcc-bugs-return-629895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 18:42:42 2019
Return-Path: <gcc-bugs-return-629895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88654 invoked by alias); 20 Jan 2019 18:42:41 -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 88501 invoked by uid 48); 20 Jan 2019 18:42:29 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65438] Unnecessary ptr check
Date: Sun, 20 Jan 2019 18:42: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: 5.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: cesar at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65438-4-15QW73RSRv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65438-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: 2019-01/txt/msg02704.txt.bz2
Content-length: 186

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

--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The code removed by the patch in comment 4 is still there.
>From gcc-bugs-return-629896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 20:17:48 2019
Return-Path: <gcc-bugs-return-629896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118426 invoked by alias); 20 Jan 2019 20:17:48 -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 118256 invoked by uid 55); 20 Jan 2019 20:17:35 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/87615] Possible excessive compile time with -O2
Date: Sun, 20 Jan 2019 20:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87615-4-B40m5mi6wN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87615-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: 2019-01/txt/msg02705.txt.bz2
Content-length: 2607

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

--- Comment #13 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Sun Jan 20 20:17:02 2019
New Revision: 268107

URL: https://gcc.gnu.org/viewcvs?rev=268107&root=gcc&view=rev
Log:
Limit AA walking in IPA summary generation

2019-01-20  Martin Jambor  <mjambor@suse.cz>

        PR ipa/87615
        * ipa-prop.h (struct ipa_func_body_info): Replaced field aa_walked
        with aa_walk_budget.
        * cgraph.h (ipa_polymorphic_call_context::get_dynamic_type): Add
        aa_walk_budget_p parameter.
        * ipa-fnsummary.c (unmodified_parm_1): New parameter fbi.  Limit AA
        walk.  Updated all callers.
        (unmodified_parm): New parameter fbi, pass it to unmodified_parm_1.
        (eliminated_by_inlining_prob): New parameter fbi, pass it on to
        unmodified_parm.
        (will_be_nonconstant_expr_predicate): New parameter fbi, removed
        parameter info.  Extract info from fbi.  Pass fbi to recursive calls
        and to unmodified_parm.
        (phi_result_unknown_predicate): New parameter fbi, removed parameter
        info, updated call to will_be_nonconstant_expr_predicate.
        (param_change_prob): New parameter fbi, limit AA walking.
        (analyze_function_body): Initialize aa_walk_budget in fbi.  Update
        calls to various above functions.
        * ipa-polymorphic-call.c (get_dynamic_type): Add aa_walk_budget_p
        parameter.  Use it to limit AA walking.
        * ipa-prop.c (detect_type_change_from_memory_writes): New parameter
        fbi, limit AA walk.
        (detect_type_change): New parameter fbi, pass it on to
        detect_type_change_from_memory_writes.
        (detect_type_change_ssa): Likewise.
        (aa_overwalked): Removed.
        (parm_preserved_before_stmt_p): Assume fbi is never NULL, stream line
        accordingly, adjust to the neew AA limiting scheme.
        (parm_ref_data_preserved_p): Likewise.
        (ipa_compute_jump_functions_for_edge): Adjust call to
        get_dynamic_type.
        (ipa_analyze_call_uses): Likewise.
        (ipa_analyze_virtual_call_uses): Pass fbi to detect_type_change_ssa.
        (ipa_analyze_node): Initialize aa_walk_budget.
        (ipcp_transform_function): Likewise.
        * tree-ssa-sccvn.c (eliminate_dom_walker::eliminate_stmt): Update call
        to get_dynamic_type.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cgraph.h
    trunk/gcc/ipa-fnsummary.c
    trunk/gcc/ipa-polymorphic-call.c
    trunk/gcc/ipa-prop.c
    trunk/gcc/ipa-prop.h
    trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-629897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 21:01:15 2019
Return-Path: <gcc-bugs-return-629897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116846 invoked by alias); 20 Jan 2019 21:01:15 -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 116639 invoked by uid 48); 20 Jan 2019 21:01:01 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Sun, 20 Jan 2019 21:01: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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:
Message-ID: <bug-88906-4-4E7DEtPV6n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg02706.txt.bz2
Content-length: 1983

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

--- Comment #3 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Before dse1 pass, we have:

    5: {r90:SI=frame:SI-0x20;clobber flags:CC;}
      REG_UNUSED flags:CC
    6: r91:SI=0
    7: r92:SI=0x4
    8: {r92:SI=0;r90:SI=r92:SI<<0x2+r90:SI;[r90:SI]=0;use r91:SI;use r92:SI;}
      REG_DEAD r91:SI
      REG_UNUSED r92:SI
      REG_UNUSED r90:SI
    9: [frame:SI-0x20]=0xffffffffffffffff
   10: [frame:SI-0x20]=0
   13: {r95:SI=frame:SI-0x10;clobber flags:CC;}
      REG_UNUSED flags:CC
   14: {r96:SI=frame:SI-0x20;clobber flags:CC;}
      REG_UNUSED flags:CC
   16: {sp:SI=sp:SI-0x4;clobber flags:CC;}
      REG_UNUSED flags:CC
      REG_ARGS_SIZE 0x4
   17: [--sp:SI]=0x10
      REG_ARGS_SIZE 0x8
   18: [--sp:SI]=r96:SI
      REG_DEAD r96:SI
      REG_ARGS_SIZE 0xc
   19: [--sp:SI]=r95:SI
      REG_DEAD r95:SI
      REG_ARGS_SIZE 0x10
   20: ax:SI=call [`memcpy'] argc:0x10
      REG_UNUSED ax:SI
      REG_EH_REGION 0

with (insn 8), (insn 9) and (insn 10) initializing area, beginning at
frame-0x20. The next insns set up arguments of the call to memcpy, where
frame-0x20 is referred as source. However, when memcpy is emitted, nothing
marks its source region as used, so dse1 pass simply removes seemingly unused
initializations, leaving:

    5: {r90:SI=frame:SI-0x20;clobber flags:CC;}
      REG_UNUSED flags:CC
    6: r91:SI=0
    7: r92:SI=0x4
   13: {r95:SI=frame:SI-0x10;clobber flags:CC;}
      REG_UNUSED flags:CC
   14: {r96:SI=frame:SI-0x20;clobber flags:CC;}
      REG_UNUSED flags:CC
   16: {sp:SI=sp:SI-0x4;clobber flags:CC;}
      REG_UNUSED flags:CC
      REG_ARGS_SIZE 0x4
   17: [--sp:SI]=0x10
      REG_ARGS_SIZE 0x8
   18: [--sp:SI]=r96:SI
      REG_DEAD r96:SI
      REG_ARGS_SIZE 0xc
   19: [--sp:SI]=r95:SI
      REG_DEAD r95:SI
      REG_ARGS_SIZE 0x10
   20: ax:SI=call [`memcpy'] argc:0x10
      REG_UNUSED ax:SI
      REG_EH_REGION 0
>From gcc-bugs-return-629898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 22:26:18 2019
Return-Path: <gcc-bugs-return-629898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35844 invoked by alias); 20 Jan 2019 22:26:18 -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 35706 invoked by uid 48); 20 Jan 2019 22:26:05 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88579] Calculating power of powers of two
Date: Sun, 20 Jan 2019 22:26: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88579-4-EMLG6iPYSF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88579-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88579-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: 2019-01/txt/msg02707.txt.bz2
Content-length: 191

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

--- Comment #4 from Harald Anlauf <anlauf at gmx dot de> ---
Patch submitted here:

https://gcc.gnu.org/ml/fortran/2019-01/msg00163.html
>From gcc-bugs-return-629899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 22:51:19 2019
Return-Path: <gcc-bugs-return-629899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83443 invoked by alias); 20 Jan 2019 22:51:19 -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 83311 invoked by uid 48); 20 Jan 2019 22:51:06 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32512] efficiency of RESHAPE and SPREAD
Date: Sun, 20 Jan 2019 22:51: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.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-32512-4-1uaAtJmXs3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32512-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32512-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: 2019-01/txt/msg02708.txt.bz2
Content-length: 491

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #8 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Is this still an actual feature request? or have things changed in the past 7
years?
>From gcc-bugs-return-629900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:01:25 2019
Return-Path: <gcc-bugs-return-629900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97538 invoked by alias); 20 Jan 2019 23:01:24 -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 97319 invoked by uid 48); 20 Jan 2019 23:01:10 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32515] [F03] Reject COMMON block names if local symbol already exists
Date: Sun, 20 Jan 2019 23:01: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.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: REOPENED
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-32515-4-D6FcVhDtln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32515-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32515-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: 2019-01/txt/msg02709.txt.bz2
Content-length: 718

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #4 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
I think Mikael Morin is incorrect here. nagfor and ifort reject the test case,
e.g. 
ifort:
A name that identifies a global entity is used to identify another global
entity in the same program.
nagfor:
Error: pr_32515.f90, line 31: COMMON block BAR is also a global procedure
So I think this should be closed.
>From gcc-bugs-return-629901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:04:11 2019
Return-Path: <gcc-bugs-return-629901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100408 invoked by alias); 20 Jan 2019 23:04:11 -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 100282 invoked by uid 48); 20 Jan 2019 23:03:58 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32986] Improve diagnostic message for COMMON with automatic object
Date: Sun, 20 Jan 2019 23:04: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.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-32986-4-0WVXaAc07m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32986-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32986-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: 2019-01/txt/msg02710.txt.bz2
Content-length: 519

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #3 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Indeed, ifort is more informative, though nagfor also just tells em
"N is not permitted in a constant expression".
>From gcc-bugs-return-629902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:08:28 2019
Return-Path: <gcc-bugs-return-629902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103911 invoked by alias); 20 Jan 2019 23:08:27 -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 103817 invoked by uid 48); 20 Jan 2019 23:08:14 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88175] Showing header file instead of source code line for uninitialized variable
Date: Sun, 20 Jan 2019 23:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot 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:
Message-ID: <bug-88175-4-6Bu97SIgVl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88175-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88175-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: 2019-01/txt/msg02711.txt.bz2
Content-length: 239

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

--- Comment #15 from Jonny Grant <jg at jguk dot org> ---
Does the implicitly created copy-constructor get saved to a file at all? Or can
it be saved to a file like -save-temps does?
>From gcc-bugs-return-629903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:09:08 2019
Return-Path: <gcc-bugs-return-629903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105081 invoked by alias); 20 Jan 2019 23:09:08 -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 104791 invoked by uid 48); 20 Jan 2019 23:08:55 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33097] Function decl trees without proper argument list
Date: Sun, 20 Jan 2019 23:09: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.2.1
X-Bugzilla-Keywords: FIXME
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-33097-4-rgPaCPJIMH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-33097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-33097-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: 2019-01/txt/msg02712.txt.bz2
Content-length: 516

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #20 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Dominique, you announced almost 10 months ago that you would close this one in
case of no feedback. Closing?
>From gcc-bugs-return-629904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:23:07 2019
Return-Path: <gcc-bugs-return-629904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116457 invoked by alias); 20 Jan 2019 23:23:07 -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 116396 invoked by uid 48); 20 Jan 2019 23:23:02 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34392] BOZ diagnost invalid Fortran 2003 use with -stdò003 warnings
Date: Sun, 20 Jan 2019 23:23: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.3.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-34392-4-TZtSron7kF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34392-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34392-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: 2019-01/txt/msg02713.txt.bz2
Content-length: 505

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #3 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Looks like one needs to come up with a list of possible cases to find one that
is not yet covered.
>From gcc-bugs-return-629905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:29:21 2019
Return-Path: <gcc-bugs-return-629905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127963 invoked by alias); 20 Jan 2019 23:29: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 127900 invoked by uid 48); 20 Jan 2019 23:29:17 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34528] Document internal structure of arrays
Date: Sun, 20 Jan 2019 23:29: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.3.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
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-34528-4-sp1SfZcV2V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34528-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34528-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: 2019-01/txt/msg02714.txt.bz2
Content-length: 517

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #2 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Is this still the same interface nowadays then it was back then? And is a
possible new one now maybe documented?
>From gcc-bugs-return-629906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:34:49 2019
Return-Path: <gcc-bugs-return-629906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49342 invoked by alias); 20 Jan 2019 23:34:49 -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 45629 invoked by uid 48); 20 Jan 2019 23:34:43 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34663] Specification expression is defined by dummy variables of different entry points
Date: Sun, 20 Jan 2019 23:34: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.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-34663-4-Gotz23X7vj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34663-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: 2019-01/txt/msg02715.txt.bz2
Content-length: 481

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #3 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Entry is now a F2008 obsolescent feature. Neither nagfor nor PGI catch this.
>From gcc-bugs-return-629907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 20 23:55:27 2019
Return-Path: <gcc-bugs-return-629907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81277 invoked by alias); 20 Jan 2019 23:55:26 -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 78970 invoked by uid 48); 20 Jan 2019 23:55:22 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34392] BOZ diagnost invalid Fortran 2003 use with -stdò003 warnings
Date: Sun, 20 Jan 2019 23:55: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.3.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl 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-34392-4-0WhTAArIkn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34392-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34392-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: 2019-01/txt/msg02716.txt.bz2
Content-length: 559

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to JÃ¼rgen Reuter from comment #3)
> Looks like one needs to come up with a list of possible cases to find one
> that is not yet covered.

BOZ handling needs to be rewritten.  I'll get to it one day.
>From gcc-bugs-return-629908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 02:27:19 2019
Return-Path: <gcc-bugs-return-629908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 883 invoked by alias); 21 Jan 2019 02:27:19 -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 778 invoked by uid 48); 21 Jan 2019 02:27:14 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88423] [9 Regression] ICE in begin_move_insn, at sched-ebb.c:175
Date: Mon, 21 Jan 2019 02:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88423-4-HjKxzJ9Qyt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88423-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: 2019-01/txt/msg02717.txt.bz2
Content-length: 416

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

Segher Boessenkool <segher at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |segher at gcc dot gnu.org

--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Is this a dup of PR88347?
>From gcc-bugs-return-629909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 04:13:13 2019
Return-Path: <gcc-bugs-return-629909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127848 invoked by alias); 21 Jan 2019 04:13:13 -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 127795 invoked by uid 48); 21 Jan 2019 04:13:08 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88932] New: [8/9 Regression] ICE: verify_ssa failed (Error: definition in block 29 does not dominate use in block 25)
Date: Mon, 21 Jan 2019 04:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88932-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: 2019-01/txt/msg02718.txt.bz2
Content-length: 1880

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

            Bug ID: 88932
           Summary: [8/9 Regression] ICE: verify_ssa failed (Error:
                    definition in block 29 does not dominate use in block
                    25)
           Product: gcc
           Version: 8.0
            Status: UNCONFIRMED
          Keywords: ice-checking, ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gfortran-9.0.0-alpha20190113 snapshot (r267906) ICEs when compiling
gcc/testsuite/gfortran.dg/assumed_rank_1.f90 w/ -fpredictive-commoning
-fno-tree-ch -fno-tree-dominator-opts -fno-tree-fre:

% powerpc-e300c3-linux-gnu-gfortran-9.0.0-alpha20190113 -O1
-fpredictive-commoning -fno-tree-ch -fno-tree-dominator-opts -fno-tree-fre -c
gcc/testsuite/gfortran.dg/assumed_rank_1.f90
gcc/testsuite/gfortran.dg/assumed_rank_1.f90:96:0:

   96 |   subroutine foo2(a, rnk, low, high, val)
      | 
Error: definition in block 29 does not dominate use in block 25
for SSA_NAME: D_lsm0.181_140 in statement:
_68 = D_lsm0.181_140;
during GIMPLE pass: pcom
gcc/testsuite/gfortran.dg/assumed_rank_1.f90:96:0: internal compiler error:
verify_ssa failed
0xfbf4e6 verify_ssa(bool, bool)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/tree-ssa.c:1188
0xcc1870 execute_function_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:1984
0xcc210a execute_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:2031

(While my target here is powerpc, the ICE not target-specific.)
>From gcc-bugs-return-629910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 04:13:20 2019
Return-Path: <gcc-bugs-return-629910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128563 invoked by alias); 21 Jan 2019 04:13: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 127853 invoked by uid 48); 21 Jan 2019 04:13:13 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] New: ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Mon, 21 Jan 2019 04:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88933-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: 2019-01/txt/msg02719.txt.bz2
Content-length: 5439

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

            Bug ID: 88933
           Summary: ICE: verify_cgraph_node failed (Error: caller edge
                    count does not match BB count)
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Keywords: ice-checking, ice-on-valid-code, openmp
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

gfortran-9.0.0-alpha20190113 snapshot (r267906) ICEs when compiling
libgomp/testsuite/libgomp.fortran/task2.f90 at any optimization level (except
-Ofast) and w/ -fexceptions -fipa-cp -fnon-call-exceptions -fopenmp
-fno-inline-functions-called-once:

% powerpc-e300c3-linux-gnu-gfortran-9.0.0-alpha20190113 -std=legacy -O1
-fexceptions -fipa-cp -fnon-call-exceptions -fopenmp
-fno-inline-functions-called-once -c
libgomp/testsuite/libgomp.fortran/task2.f90
libgomp/testsuite/libgomp.fortran/task2.f90:18:0:

   18 |   subroutine foo (c, d, e, f, g, h, i, j, k, n)
      | 
Error: caller edge count does not match BB count
edge count: 748404 (estimated locally)
 bb count: 1804253 (estimated locally)
libgomp/testsuite/libgomp.fortran/task2.f90:18:0: Error: caller edge count does
not match BB count
edge count: 30269084 (estimated locally)
 bb count: 72972719 (estimated locally)
foo.2124.constprop.0/27 (foo.constprop) @0x7fb992431b40
  Type: function definition analyzed
  Visibility: artificial
  References: 
  Referring: 
  Availability: local
  Function flags: count:1804252 (estimated locally) body local
  Called by: test/0 (6137140 (estimated locally),1.00 per call) (can throw
external) 
  Calls: __builtin_stack_save/20 (1804252 (estimated locally),1.00 per call)
__builtin_alloca_with_align/21 (1804252 (estimated locally),1.00 per call)
__builtin_malloc/22 (1804252 (estimated locally),1.00 per call)
__builtin_malloc/22 (1804252 (estimated locally),1.00 per call)
__builtin_malloc/22 (1804252 (estimated locally),1.00 per call)
__builtin_memcpy/14 (532254 (estimated locally),0.29 per call)
__builtin_memset/23 (532254 (estimated locally),0.29 per call)
__builtin_memcpy/14 (532254 (estimated locally),0.29 per call)
__builtin_memcpy/14 (6649989 (estimated locally),3.69 per call)
__builtin_memset/23 (6649989 (estimated locally),3.69 per call)
__builtin_memcpy/14 (6649989 (estimated locally),3.69 per call)
__builtin_memcpy/14 (6649989 (estimated locally),3.69 per call)
__builtin_memset/23 (6649989 (estimated locally),3.69 per call)
__builtin_memcpy/14 (6649989 (estimated locally),3.69 per call)
__builtin_GOMP_task/24 (1804253 (estimated locally),1.00 per call)
__builtin_memset/23 (748404 (estimated locally),0.41 per call)
__builtin_memset/23 (748404 (estimated locally),0.41 per call)
__builtin_memset/23 (30269084 (estimated locally),16.78 per call)
__builtin_memset/23 (30269087 (estimated locally),16.78 per call)
__builtin_memset/23 (748405 (estimated locally),0.41 per call)
__builtin_free/25 (1804255 (estimated locally),1.00 per call) __builtin_free/25
(1804255 (estimated locally),1.00 per call) __builtin_free/25 (1804255
(estimated locally),1.00 per call) __builtin_stack_restore/26 (1804255
(estimated locally),1.00 per call) __builtin_free/25 (0 (precise),0.00 per
call) __builtin_free/25 (0 (precise),0.00 per call) __builtin_free/25 (0
(precise),0.00 per call) 
during IPA pass: inline
libgomp/testsuite/libgomp.fortran/task2.f90:18:0: internal compiler error:
verify_cgraph_node failed
0x97940f cgraph_node::verify_node()
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cgraph.c:3430
0x96d134 symtab_node::verify()
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/symtab.c:1218
0xe288f9 optimize_inline_calls(tree_node*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/tree-inline.c:5060
0x15347d4 inline_transform(cgraph_node*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/ipa-inline-transform.c:682
0xcc4454 execute_one_ipa_transform_pass
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:2225
0xcc4454 execute_all_ipa_transforms()
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:2264
0x98053c cgraph_node::expand()
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cgraphunit.c:2189
0x981a0d expand_all_functions
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cgraphunit.c:2334
0x981a0d symbol_table::compile()
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cgraphunit.c:2685
0x983db8 symbol_table::finalize_compilation_unit()
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cgraphunit.c:2863

(While my target here is powerpc, the ICE not target-specific.)
>From gcc-bugs-return-629911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 04:35:59 2019
Return-Path: <gcc-bugs-return-629911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125623 invoked by alias); 21 Jan 2019 04:35:59 -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 125547 invoked by uid 48); 21 Jan 2019 04:35:54 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88934] New: [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 04:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88934-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: 2019-01/txt/msg02720.txt.bz2
Content-length: 2520

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

            Bug ID: 88934
           Summary: [9 Regression] ICE: verify_gimple failed (Error:
                    mismatching comparison operand types)
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-checking, ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---
            Target: powerpc-e300c3-linux-gnu

gfortran-9.0.0-alpha20190113 snapshot (r267906) ICEs when compiling
gcc/testsuite/gfortran.dg/matmul_6.f90 w/ -mvsx -O1 (-O2, -Os) -ftree-vectorize
(maybe -m32 is also needed):

% powerpc-e300c3-linux-gnu-gfortran-9.0.0-alpha20190113 -mvsx -O1
-ftree-vectorize -c gcc/testsuite/gfortran.dg/matmul_6.f90
gcc/testsuite/gfortran.dg/matmul_6.f90:7:0:

    7 | program main
      | 
Error: mismatching comparison operand types
vector(4) unsigned int
vector(4) <unnamed type>
vect_patt_410.97_511 = VEC_COND_EXPR <vect__590.95_610 != vect_cst__627,
vect_cst__157, vect_cst__207>;
gcc/testsuite/gfortran.dg/matmul_6.f90:7:0: Error: mismatching comparison
operand types
vector(4) unsigned int
vector(4) <unnamed type>
vect_patt_410.97_521 = VEC_COND_EXPR <vect__590.96_616 != vect_cst__626,
vect_cst__371, vect_cst__5>;
gcc/testsuite/gfortran.dg/matmul_6.f90:7:0: Error: mismatching comparison
operand types
vector(4) unsigned int
vector(4) <unnamed type>
vect_patt_540.105_142 = VEC_COND_EXPR <vect__546.103_375 != vect_cst__489,
vect_cst__254, vect_cst__430>;
gcc/testsuite/gfortran.dg/matmul_6.f90:7:0: Error: mismatching comparison
operand types
vector(4) unsigned int
vector(4) <unnamed type>
vect_patt_540.105_361 = VEC_COND_EXPR <vect__546.104_13 != vect_cst__479,
vect_cst__14, vect_cst__129>;
during GIMPLE pass: slp
gcc/testsuite/gfortran.dg/matmul_6.f90:7:0: internal compiler error:
verify_gimple failed
0xdeb409 verify_gimple_in_cfg(function*, bool)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/tree-cfg.c:5422
0xcc176e execute_function_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:1977
0xcc210a execute_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:2031
>From gcc-bugs-return-629912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:46:27 2019
Return-Path: <gcc-bugs-return-629912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104007 invoked by alias); 21 Jan 2019 05:46:24 -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 103097 invoked by uid 48); 21 Jan 2019 05:46:09 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] New: std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88935-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: 2019-01/txt/msg02721.txt.bz2
Content-length: 5266

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

            Bug ID: 88935
           Summary: std::random_shuffle does not work if the sequence is
                    longer than RAND_MAX elements
           Product: gcc
           Version: 8.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: giovannibajo at gmail dot com
  Target Milestone: ---

The problem we faced is an heavy non-uniform distribution of probabilities
with the result of std::random_shuffle when the number of elements in the
sequence is big compared to RAND_MAX.

In the specific the problem become appearent after investigating the bad
performance of an algorithm that was discovered being originated by a bad
shuffling of the pixel positions of an image.

To clearly see the problem of the skewed distribution consider the following
code:

    #include <stdio.h>
    #include <algorithm>
    #include <vector>

    int main(int argc, const char *argv[]) {
        int w = 512, h = 512;

        // all pixels black at start
        std::vector<unsigned char> img(w*h);

        // Create a list of all pixels
        std::vector<int> pixels(w*h);
        for (int i=0; i<w*h; i++) pixels[i] = i;

        // Shuffle them and keep only the first 10000
        std::random_shuffle(pixels.begin(), pixels.end());
        pixels.resize(10000);

        // Set those pixels to white
        for (auto& i : pixels) img[i] = 0xFF;

        // Save result
        FILE *f = fopen("out.pgm", "wb");
        fprintf(f, "P5\n%i %i 255\n", w, h);
        fwrite(&img[0], 1, w*h, f);
        fclose(f);

        return 0;
    }

The output produced by g++ is good.png, the output produced by
unpatched mingw is bad.png.

Investigating on the reasons the problem seems to be however in g++
code: the random_shuffle code (stl_algo.h) is implemented with

      if (__first != __last)
          for (_RandomAccessIterator __i = __first + 1; __i != __last; ++__i)
          {
              // XXX rand() % N is not uniformly distributed
              _RandomAccessIterator __j = __first
                  + std::rand() % ((__i - __first) + 1);
              if (__i != __j)
                  std::iter_swap(__i, __j);
          }

The cited problem of rand()%N not being uniform is catastrophic in our
case, because std::rand() produces on windows libc a value that is <=
32767 (RAND_MAX) and we're shuffling a much bigger array.

32767 is allowed by the standard definition of RAND_MAX, but this
means that std::rand() should not be used to get random numbers
bigger than RAND_MAX.

In the case of the test program the sequence size is 512*512=262144
elements and the random_shuffle algorithm performs very poorly when
RAND_MAX is 32767 (it's so bad we found the problem not by examining
the shuffling, but by the investigating on bad performance - only on
the windows version - of a much bigger program that was using a
shuffling operation as an initial internal step).

The generated distribution is bad even if the size is smaller (but not
a lot smaller) than RAND_MAX... and it's due to the problem cited in
the comment in the code. Consider:

  RAND_MAX = 39  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  N = 30         yyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
  rand()%N       xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                 xxxxxxxxxx

  N = 12         zzzzzzzzzzzz
  rand()%N       xxxxxxxxxxxx
                 xxxxxxxxxxxx
                 xxxxxxxxxxxx
                 xxxx

In the case of N=30 numbers from 0 to 9 have twice the probability
than the remaining numbers. In the case of N=12 instead then numbers
from 0 to 3 have 4/3 times the probability of remaining numbers.
The terrible behaviour is when N > RAND_MAX and in this case the
ratio is infinite (some numbers have zero probability because "x"s
are not enough!).

When using random_shuffle this is not very evident at a first sight
on a single shuffle unless N is much bigger than RAND_MAX (what
happened to us) but plotting a chart of the average value of x[i]
after a shuffle operation makes the problem evident even when the
value is smaller but not much smaller.

chart.png shows the average of x[i] on 10000 random shuffle operations
performed simulating a RAND_MAX of 32767 with an array of 24576
elements (3/4 of RAND_MAX). Of course the "correct" plot for an
equidistributed random_shuffle should be a flat horizontal line.

chart.cpp code used to produce the data for charts is

    #include <stdio.h>
    #include <stdlib.h>
    #include <vector>
    #include <algorithm>

    int main(int argc, const char *argv[]) {
        int N = argc > 1 ? atoi(argv[1]) : 32768;
        std::vector<long long> data(N), total(N);

        for (int i=0; i<10000; i++) {
            for (int j=0; j<N; j++) data[j] = j;
            for (int j=1; j<N; j++) {
                int k = rand() % 32768 % (j+1);
                std::swap(data[j], data[k]);
            }
            for (int j=0; j<N; j++) total[j] += data[j];
        }

        for (int i=0; i<N; i++) {
            printf("%.18g\n", total[i]/10000.0);
        }

        return 0;
    }
>From gcc-bugs-return-629914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:47:31 2019
Return-Path: <gcc-bugs-return-629914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107801 invoked by alias); 21 Jan 2019 05:47:30 -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 107738 invoked by uid 48); 21 Jan 2019 05:47:26 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88935-4-Dd6acNoKeg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02723.txt.bz2
Content-length: 267

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

--- Comment #2 from Giovanni Bajo <giovannibajo at gmail dot com> ---
Created attachment 45471
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45471&action=edit
Test code to draw a chart of distributions
>From gcc-bugs-return-629913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:47:00 2019
Return-Path: <gcc-bugs-return-629913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106857 invoked by alias); 21 Jan 2019 05:47:00 -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 106684 invoked by uid 48); 21 Jan 2019 05:46:56 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88935-4-YIl1TxPzdR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02722.txt.bz2
Content-length: 251

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

--- Comment #1 from Giovanni Bajo <giovannibajo at gmail dot com> ---
Created attachment 45470
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45470&action=edit
Test code to reproduce bug
>From gcc-bugs-return-629916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:48:52 2019
Return-Path: <gcc-bugs-return-629916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110289 invoked by alias); 21 Jan 2019 05:48:52 -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 110103 invoked by uid 48); 21 Jan 2019 05:48:42 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88935-4-U8kCisGznT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02725.txt.bz2
Content-length: 284

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

--- Comment #4 from Giovanni Bajo <giovannibajo at gmail dot com> ---
Created attachment 45473
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45473&action=edit
What test.cpp actually does output with std::random_shuffle
>From gcc-bugs-return-629915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:48:00 2019
Return-Path: <gcc-bugs-return-629915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108755 invoked by alias); 21 Jan 2019 05:48:00 -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 108652 invoked by uid 48); 21 Jan 2019 05:47:56 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88935-4-IUcygUUjKw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02724.txt.bz2
Content-length: 277

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

--- Comment #3 from Giovanni Bajo <giovannibajo at gmail dot com> ---
Created attachment 45472
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45472&action=edit
What test.cpp should output if random_shuffle worked
>From gcc-bugs-return-629917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:49:26 2019
Return-Path: <gcc-bugs-return-629917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111325 invoked by alias); 21 Jan 2019 05:49:25 -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 111276 invoked by uid 48); 21 Jan 2019 05:49:21 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88935-4-aijy9PiYYV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02726.txt.bz2
Content-length: 289

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

--- Comment #5 from Giovanni Bajo <giovannibajo at gmail dot com> ---
Created attachment 45474
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45474&action=edit
Chart generated by chart.cpp that highlights broken distribution
>From gcc-bugs-return-629918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 05:51:00 2019
Return-Path: <gcc-bugs-return-629918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113519 invoked by alias); 21 Jan 2019 05:50:59 -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 113456 invoked by uid 48); 21 Jan 2019 05:50:55 -0000
From: "giovannibajo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 05:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: giovannibajo at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88935-4-3wIByUN9D6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02727.txt.bz2
Content-length: 209

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

--- Comment #6 from Giovanni Bajo <giovannibajo at gmail dot com> ---
A patch has been posted here:
https://gcc.gnu.org/ml/libstdc++/2018-12/msg00038.html
>From gcc-bugs-return-629919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 06:28:26 2019
Return-Path: <gcc-bugs-return-629919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103291 invoked by alias); 21 Jan 2019 06:28:26 -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 103229 invoked by uid 48); 21 Jan 2019 06:28:21 -0000
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88897] Bogus maybe-uninitialized warning on class field
Date: Mon, 21 Jan 2019 06:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rafael at espindo dot la
X-Bugzilla-Status: UNCONFIRMED
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: attachments.isobsolete attachments.created
Message-ID: <bug-88897-4-LtzCW2Nm0k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88897-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88897-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: 2019-01/txt/msg02728.txt.bz2
Content-length: 1066

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

Rafael Avila de Espindola <rafael at espindo dot la> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45452|0                           |1
        is obsolete|                            |
  Attachment #45453|0                           |1
        is obsolete|                            |

--- Comment #4 from Rafael Avila de Espindola <rafael at espindo dot la> ---
Created attachment 45475
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45475&action=edit
testcase

Now that I know what to look for I reduced the testcase again trying to make
sure to not introduce uninitialized uses in the process.

As far as I can tell the warning in the attached testcase is wrong.

First an optional is constructed, but _M_engaged is false since it doesn't hold
a value.

It is then moved, but move constructor checks __other._M_engaged, so the
temporary_buffer move constructor should never be called.
>From gcc-bugs-return-629920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 07:22:02 2019
Return-Path: <gcc-bugs-return-629920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80802 invoked by alias); 21 Jan 2019 07:22:01 -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 80694 invoked by uid 48); 21 Jan 2019 07:21:56 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88912] Fortran compiler segfaults when pre-include file is not found
Date: Mon, 21 Jan 2019 07:22: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88912-4-9nKJOCseFl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88912-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88912-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: 2019-01/txt/msg02729.txt.bz2
Content-length: 260

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

--- Comment #5 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
May I close the issue as invalid? As noted by Jakub, the option should not be
used by users directly and is not documented right now.
>From gcc-bugs-return-629921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 07:23:03 2019
Return-Path: <gcc-bugs-return-629921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3345 invoked by alias); 21 Jan 2019 07:23:03 -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 130561 invoked by uid 48); 21 Jan 2019 07:22:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88912] Fortran compiler segfaults when pre-include file is not found
Date: Mon, 21 Jan 2019 07:23: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88912-4-Ilhvj1Ys7O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88912-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88912-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: 2019-01/txt/msg02730.txt.bz2
Content-length: 168

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
No, you should add a proper error for that case.
>From gcc-bugs-return-629922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 07:42:45 2019
Return-Path: <gcc-bugs-return-629922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54508 invoked by alias); 21 Jan 2019 07:42:45 -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 54431 invoked by uid 48); 21 Jan 2019 07:42:41 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Mon, 21 Jan 2019 07:42: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: umesh.kalappa0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88877-4-VHY53WisI7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg02731.txt.bz2
Content-length: 493

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

--- Comment #15 from Umesh Kalappa <umesh.kalappa0 at gmail dot com> ---
like jakub recommended in the other mail thread ,

All the callers of emit_library_call* would need to be changed to pass
triplets rtx, machine_mode, int/bool /*unsignedp*/, instead of just
rtx_mode_t pair or add a new set of emit_library_call* APIs that would take
those triplets.

we feel thats clean fix ,but needs exhaust testing here (impact on other
targets).
>From gcc-bugs-return-629923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 07:50:07 2019
Return-Path: <gcc-bugs-return-629923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107281 invoked by alias); 21 Jan 2019 07:50:07 -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 107198 invoked by uid 48); 21 Jan 2019 07:50:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Mon, 21 Jan 2019 07:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-88933-4-7LVmcIN9XU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg02732.txt.bz2
Content-length: 650

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-21
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, let me take the PR.
>From gcc-bugs-return-629924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 07:54:03 2019
Return-Path: <gcc-bugs-return-629924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111643 invoked by alias); 21 Jan 2019 07:54:03 -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 111568 invoked by uid 48); 21 Jan 2019 07:53:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzg4OTA4XSBbOSBSZWdyZXNzaW9uXSBJQ0UgaW4gdHJl?= =?UTF-8?B?ZSBjaGVjazogZXhwZWN0ZWQgdHJlZSB0aGF0IGNvbnRhaW5zIOKAmGRlY2wg?= =?UTF-8?B?Y29tbW9u4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpbmRpcmVjdF9yZWbigJkg?= =?UTF-8?B?aW4gZ2ZjX2NvbnZfZ2ZjX2Rlc2NfdG9fY2ZpX2Rlc2MsIGF0IGZvcnRyYW4v?= =?UTF-8?B?dHJhbnMtZXhwci5jOjQ5Mjc=?Date: Mon, 21 Jan 2019 07:54: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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-88908-4-LfQ9cxa8uf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88908-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88908-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: 2019-01/txt/msg02733.txt.bz2
Content-length: 151

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

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Great, thanks for the fix.
>From gcc-bugs-return-629925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 07:58:39 2019
Return-Path: <gcc-bugs-return-629925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119681 invoked by alias); 21 Jan 2019 07:58:39 -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 119337 invoked by uid 48); 21 Jan 2019 07:58:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 07:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: bug_status cf_reconfirmed_on cc component everconfirmed
Message-ID: <bug-88934-4-eTGLFVKoud@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02734.txt.bz2
Content-length: 2525

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
                 CC|                            |marxin at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org
          Component|middle-end                  |tree-optimization
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, there's a minimal test-case:

$ cat matmul.f90
integer, parameter :: a=3
  integer , dimension(a,a) :: b 
  logical, dimension(a,a) :: c 

  do i=0,1
     b = ltoi(c)
     do j=0,if
        if (anymatmul(b) /= 0) then
        end if
     end do
  end do
contains
  elemental function ltoi(d)

    logical, intent(in) :: d
    if (d) then
       ltoi = 1
    else
       ltoi = 0
    end if
  end  
end 

$ ./xgcc -B. -c -mvsx -O1 -ftree-vectorize matmul.f90
matmul.f90:5:0:

    5 |   do i=0,1
      | 
Error: mismatching comparison operand types
vector(4) unsigned int
vector(4) <unnamed type>
vect_patt_43.17_16 = VEC_COND_EXPR <vect__60.15_91 != vect_cst__9,
vect_cst__17, vect_cst__12>;
matmul.f90:5:0: Error: mismatching comparison operand types
vector(4) unsigned int
vector(4) <unnamed type>
vect_patt_43.17_34 = VEC_COND_EXPR <vect__60.16_97 != vect_cst__46,
vect_cst__10, vect_cst__6>;
during GIMPLE pass: slp
matmul.f90:5:0: internal compiler error: verify_gimple failed
0xd73ba7 verify_gimple_in_cfg(function*, bool)
        ../../gcc/tree-cfg.c:5422
0xc5b6df execute_function_todo
        ../../gcc/passes.c:1977
0xc5c60e execute_todo
        ../../gcc/passes.c:2031
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

$ ./xgcc -v
Using built-in specs.
COLLECT_GCC=./xgcc
Target: powerpc-linux-gnu
Configured with: ../configure --enable-languages=c,c++,fortran
--disable-multilib --prefix=/home/marxin/bin/gcc2 --disable-bootstrap
--disable-libsanitizer --target=powerpc-linux-gnu
--with-as=/usr/bin/powerpc-suse-linux-as
Thread model: posix
gcc version 9.0.0 20190121 (experimental) (GCC) 

Richi can you please take a look?
>From gcc-bugs-return-629926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:02:04 2019
Return-Path: <gcc-bugs-return-629926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123427 invoked by alias); 21 Jan 2019 08:02: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 123340 invoked by uid 48); 21 Jan 2019 08:02:00 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88932] [8/9 Regression] ICE: verify_ssa failed (Error: definition in block 29 does not dominate use in block 25)
Date: Mon, 21 Jan 2019 08:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88932-4-1Xq1NR3I9k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88932-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: 2019-01/txt/msg02735.txt.bz2
Content-length: 828

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
                 CC|                            |amker at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
      Known to work|                            |7.3.0
   Target Milestone|---                         |8.3
     Ever confirmed|0                           |1
      Known to fail|                            |8.2.0, 9.0

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, started with r254778.
>From gcc-bugs-return-629927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:04:16 2019
Return-Path: <gcc-bugs-return-629927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128196 invoked by alias); 21 Jan 2019 08:04:16 -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 128118 invoked by uid 48); 21 Jan 2019 08:04:10 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88932] [8/9 Regression] ICE: verify_ssa failed (Error: definition in block 29 does not dominate use in block 25)
Date: Mon, 21 Jan 2019 08:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker 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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88932-4-m9lfoxg2Xc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88932-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: 2019-01/txt/msg02736.txt.bz2
Content-length: 173

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

--- Comment #2 from bin cheng <amker at gcc dot gnu.org> ---
Sorry for the breakage, I will investigate this.

Thanks,
>From gcc-bugs-return-629928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:07:10 2019
Return-Path: <gcc-bugs-return-629928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2816 invoked by alias); 21 Jan 2019 08:07: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 2699 invoked by uid 48); 21 Jan 2019 08:07:06 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33097] Function decl trees without proper argument list
Date: Mon, 21 Jan 2019 08:07: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.2.1
X-Bugzilla-Keywords: FIXME
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig 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: bug_status cc blocked
Message-ID: <bug-33097-4-gmO6uhd2fH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-33097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-33097-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: 2019-01/txt/msg02737.txt.bz2
Content-length: 1004

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |tkoenig at gcc dot gnu.org
             Blocks|                            |87689, 40976

--- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Please don't close.

This is one of the longstanding issues with gfortran, which
causes, or is closely related, to other PRs. Some might even
be duplicates.

For one thing, this kind of thing causes problems for LTO,
and also wrong-code issues such as PR 87689.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40976
[Bug 40976] Merge DECL of procedure call with DECL of gfc_get_function_type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87689
[Bug 87689] Memory corruption on Power 8
>From gcc-bugs-return-629929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:25:53 2019
Return-Path: <gcc-bugs-return-629929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51486 invoked by alias); 21 Jan 2019 08:25:52 -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 50779 invoked by uid 48); 21 Jan 2019 08:25:46 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] New: -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 08:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88936-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: 2019-01/txt/msg02738.txt.bz2
Content-length: 1846

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

            Bug ID: 88936
           Summary: -fipa-pta breaks bash (incorrect optimisation of
                    recursive static function)
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: slyfox at inbox dot ru
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Initially bug is observed by muffindrake on #gentoo-portage as a series of
mysterious bash failures.

Here is the minimal reproducer:

  #include <stdio.h>

  /*
   How to reproduce:

  $ gcc -O2 -Wall -fno-stack-protector           main.c -o c-bug         &&
./c-bug
  ff(1) = 1
  $ gcc -O2 -Wall -fno-stack-protector -fipa-pta main.c -o c-bug-ipa-pta &&
./c-bug-ipa-pta
  ff(1) = 3
  */

  static long bug (long depth, long * v)
  {
    if (depth == 0)
    {
      *v = 0;
      return 1;
    }

    long r = 1;
    long val = bug(depth - 1, &r);
    return 2 * r + val;
  }

  static long ff (long depth)
  {
    return bug(depth, (long*)NULL);
  }

  int main() {
    fprintf(stderr, "ff(1) = %ld\n", ff(1));
  }

Reproducible on 9.0.0 20190120, 8.2.0, 7.4.0, 6.5.0. Not reproducible on 5.5.0.
Reproducible on multiple platforms.

$ ./xgcc -B. -v
Reading specs from ./specs
COLLECT_GCC=./xgcc
COLLECT_LTO_WRAPPER=./lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --enable-languages=c,c++ --disable-bootstrap
--with-multilib-list=m64
--prefix=/home/slyfox/dev/git/gcc-native/../gcc-native-quick-installed
--disable-nls CFLAGS='-O0 -g ' CXXFLAGS='-O0 -g '
--with-sysroot=/usr/x86_64-HEAD-linux-gnu
Thread model: posix
gcc version 9.0.0 20190120 (experimental) (GCC)
>From gcc-bugs-return-629930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:26:59 2019
Return-Path: <gcc-bugs-return-629930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54900 invoked by alias); 21 Jan 2019 08:26:58 -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 54221 invoked by uid 48); 21 Jan 2019 08:26:52 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88936-4-bKUExjFLqJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02739.txt.bz2
Content-length: 229

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

--- Comment #1 from Sergei Trofimovich <slyfox at inbox dot ru> ---
Created attachment 45476
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45476&action=edit
main,c
>From gcc-bugs-return-629931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:29:07 2019
Return-Path: <gcc-bugs-return-629931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61874 invoked by alias); 21 Jan 2019 08:29:06 -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 61802 invoked by uid 48); 21 Jan 2019 08:29:02 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 08:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88936-4-e4VwJFsHqo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02740.txt.bz2
Content-length: 382

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

--- Comment #2 from Sergei Trofimovich <slyfox at inbox dot ru> ---
The sample output different result with -fipa-pta and without.

$ gcc -O2 -Wall -fno-stack-protector           main.c -o c-bug         &&
./c-bug
ff(1) = 1
$ gcc -O2 -Wall -fno-stack-protector -fipa-pta main.c -o c-bug-ipa-pta &&
./c-bug-ipa-pta
ff(1) = 3
>From gcc-bugs-return-629932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:32:10 2019
Return-Path: <gcc-bugs-return-629932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64924 invoked by alias); 21 Jan 2019 08:32:09 -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 64838 invoked by uid 48); 21 Jan 2019 08:32:03 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88937] New: valgrind error in parse_has_include
Date: Mon, 21 Jan 2019 08:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88937-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: 2019-01/txt/msg02741.txt.bz2
Content-length: 1660

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

            Bug ID: 88937
           Summary: valgrind error in parse_has_include
           Product: gcc
           Version: 8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For a valgrind build of recent gcc trunk and the test file
./g++.dg/cpp1y/feat-cxx14.C, I get 

$ ~/gcc/results/bin/gcc -c ./g++.dg/cpp1y/feat-cxx14.C
In file included from ./g++.dg/cpp1y/feat-cxx14.C:290:
./g++.dg/cpp1y/phoobhar.h:14:6: error: #error
"__has_include_next(\"phoobhar.h\")"
   14 | #    error "__has_include_next(\"phoobhar.h\")"
      |      ^~~~~
==21093== Conditional jump or move depends on uninitialised value(s)
==21093==    at 0x13D7C48: parse_has_include(cpp_reader*, include_type)
(expr.c:2247)
==21093==    by 0x13DAF33: eval_token (expr.c:1159)
==21093==    by 0x13DAF33: _cpp_parse_expr (expr.c:1328)
==21093==    by 0x13D36BC: do_if(cpp_reader*) (directives.c:2008)
$ ~/gcc/results/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/dcb/gcc/results/bin/gcc
COLLECT_LTO_WRAPPER=/home/dcb/gcc/results.268000.valgrind/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../trunk/configure
--prefix=/home/dcb/gcc/results.268000.valgrind --disable-bootstrap
--disable-multilib --disable-werror --enable-checking=valgrind
--enable-languages=c,c++,fortran
Thread model: posix
gcc version 9.0.0 20190117 (experimental) (GCC) 
$
>From gcc-bugs-return-629933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:33:56 2019
Return-Path: <gcc-bugs-return-629933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77805 invoked by alias); 21 Jan 2019 08:33:56 -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 77726 invoked by uid 48); 21 Jan 2019 08:33:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-88936-4-1hWrv12gBl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02742.txt.bz2
Content-length: 1112

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |6.4.0
           Keywords|                            |wrong-code
   Last reconfirmed|                            |2019-01-21
                 CC|                            |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1
            Summary|-fipa-pta breaks bash       |[7/8/9 Regression]
                   |(incorrect optimisation of  |-fipa-pta breaks bash
                   |recursive static function)  |(incorrect optimisation of
                   |                            |recursive static function)
   Target Milestone|---                         |7.5
      Known to fail|                            |7.3.0, 8.2.0, 9.0

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, started with r231498.
>From gcc-bugs-return-629934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:39:02 2019
Return-Path: <gcc-bugs-return-629934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112435 invoked by alias); 21 Jan 2019 08:39:02 -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 109699 invoked by uid 48); 21 Jan 2019 08:38:57 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] New: ICE in extract_insn, at recog.c:2304
Date: Mon, 21 Jan 2019 08:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost
Message-ID: <bug-88938-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: 2019-01/txt/msg02743.txt.bz2
Content-length: 1605

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

            Bug ID: 88938
           Summary: ICE in extract_insn, at recog.c:2304
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu

Very old ICE:

$ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/tbm-bextri-1.c
-fno-tree-ccp -mtbm -Og -fno-tree-fre
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/tbm-bextri-1.c: In
function â€˜mainâ€™:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/tbm-bextri-1.c:36:1:
error: unrecognizable insn:
 }
 ^
(insn 5 2 6 2 (parallel [
            (set (reg:SI 102 [ _24 ])
                (zero_extract:SI (const_int -1 [0xffffffffffffffff])
                    (const_int 0 [0])
                    (const_int 0 [0])))
            (clobber (reg:CC 17 flags))
        ]) "/usr/lib64/gcc/x86_64-suse-linux/8/include/tbmintrin.h":41 -1
     (nil))
during RTL pass: vregs
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/tbm-bextri-1.c:36:1:
internal compiler error: in extract_insn, at recog.c:2304
0x7ffff6996fea __libc_start_main
        ../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://bugs.opensuse.org/> for instructions.
>From gcc-bugs-return-629935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:44:30 2019
Return-Path: <gcc-bugs-return-629935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85080 invoked by alias); 21 Jan 2019 08:44:30 -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 85031 invoked by uid 48); 21 Jan 2019 08:44:26 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88939] New: [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort
Date: Mon, 21 Jan 2019 08:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88939-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: 2019-01/txt/msg02744.txt.bz2
Content-length: 1737

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

            Bug ID: 88939
           Summary: [nvptx, openacc, libgomp] Assertion `!s->map->active'
                    failed for synchronous parallel with abort
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Atm, abort-1.c passes like this:
...
CheCKpOInT

libgomp: cuStreamSynchronize error: an illegal instruction was encountered
abort-1.exe: /libgomp/plugin/plugin-nvptx.c:271: map_fini: \
  Assertion `!s->map->active' failed.
PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/abort-1.c \
  -DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0  -O0  execution test
...

The usual scenario in nvptx_exec for synchronous kernel launches is this
sequence of calls:
- map_push, allocating a device memory pointer for the kernel arguments, and
  allocating a struct cuda_map (to keep track of the device pointer), setting
  the active field of struct cuda_map to true
- cuLaunchKernel, launching a kernel on a CUDA stream
- cuStreamSynchronize, waiting till the stream task (i.e, the kernel) completes
- map_pop, freeing the device memory and the corresponding struct cuda_map

In the case of this test-case, the abort causes cuStreamSynchronize to return
CUDA_ERROR_ILLEGAL_INSTRUCTION, which is then handled using a GOMP_PLUGIN_fatal
call, which calls abort. This means map_pop is not called, so no memory is
freed.

Then during fini_streams_for_device, map_fini is called, the remaining map is
found, and the !s->map->active assert triggers.
>From gcc-bugs-return-629936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:55:08 2019
Return-Path: <gcc-bugs-return-629936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106457 invoked by alias); 21 Jan 2019 08:55:08 -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 103775 invoked by uid 48); 21 Jan 2019 08:55:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88915] Try smaller vectorisation factors in scalar fallback
Date: Mon, 21 Jan 2019 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88915-4-oWdOZfdPz9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88915-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88915-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: 2019-01/txt/msg02745.txt.bz2
Content-length: 545

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yeah, the epilogue stuff is on my list of things to revisit for GCC 10.
>From gcc-bugs-return-629937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 08:58:18 2019
Return-Path: <gcc-bugs-return-629937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34900 invoked by alias); 21 Jan 2019 08:58:18 -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 28771 invoked by uid 48); 21 Jan 2019 08:58:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators
Date: Mon, 21 Jan 2019 08:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: cf_gcctarget bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88916-4-lLcK8J5MU5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88916-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: 2019-01/txt/msg02746.txt.bz2
Content-length: 554

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-*, i?86-*-*
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-629938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:01:11 2019
Return-Path: <gcc-bugs-return-629938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88268 invoked by alias); 21 Jan 2019 09:01:11 -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 87959 invoked by uid 48); 21 Jan 2019 09:00:50 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88915] Try smaller vectorisation factors in scalar fallback
Date: Mon, 21 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov 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:
Message-ID: <bug-88915-4-ZMh29K70dM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88915-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88915-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: 2019-01/txt/msg02747.txt.bz2
Content-length: 407

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

--- Comment #2 from ktkachov at gcc dot gnu.org ---
(In reply to Richard Biener from comment #1)
> Yeah, the epilogue stuff is on my list of things to revisit for GCC 10.

I think this isn't necessarily about the epilogue (the main vector loop is not
entered here), but rather the scalar fallback.

Unless we merge the fallback and epilogue into one.
>From gcc-bugs-return-629939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:10:00 2019
Return-Path: <gcc-bugs-return-629939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102198 invoked by alias); 21 Jan 2019 09:09:59 -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 102106 invoked by uid 48); 21 Jan 2019 09:09:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88919] New test case gcc.dg/vect/pr88903-1.c in r268076 fails
Date: Mon, 21 Jan 2019 09:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88919-4-8PnRRgXzyy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88919-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: 2019-01/txt/msg02748.txt.bz2
Content-length: 818

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Passes for me on x86_64-linux.  Can you investigate a bit more?  The key
observation should be that compared to before the rev. the loop

  for (int i = 0; i < 512; ++i)
    {
      x[2*i] = x[2*i] << (i+1);
      x[2*i+1] = x[2*i+1] << (i+1);
    }

should be vectorized using a vector << vector shift (rather than
vector << scalar).
>From gcc-bugs-return-629941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:13:48 2019
Return-Path: <gcc-bugs-return-629941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26267 invoked by alias); 21 Jan 2019 09:13:48 -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 26173 invoked by uid 48); 21 Jan 2019 09:13:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-88920-4-lrRp1UjSPb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02750.txt.bz2
Content-length: 614

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Also just saw that on x86_64-linux.
>From gcc-bugs-return-629940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:13:37 2019
Return-Path: <gcc-bugs-return-629940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25451 invoked by alias); 21 Jan 2019 09:13:36 -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 25384 invoked by uid 48); 21 Jan 2019 09:13:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Mon, 21 Jan 2019 09:13: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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-88906-4-tCHHX0LR7y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg02749.txt.bz2
Content-length: 577

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Hard to bisect, because before r233979 this used to ICE or segfault in the
compiler, starting with r201645 when -mmemcpy-strategy= option has been added,
and already r233979 generates wrong-code.
>From gcc-bugs-return-629942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:17:41 2019
Return-Path: <gcc-bugs-return-629942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36213 invoked by alias); 21 Jan 2019 09:17:41 -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 36158 invoked by uid 48); 21 Jan 2019 09:17:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88922] Merge identical constants with different modes
Date: Mon, 21 Jan 2019 09:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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-88922-4-7uYpAW6p9r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88922-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: 2019-01/txt/msg02751.txt.bz2
Content-length: 547

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
IIRC I had patches to do this.  My main target was vector float constants vs
scalar float constants.  Can't find the patch though (it's >10 years old
I think...)
>From gcc-bugs-return-629943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:20:42 2019
Return-Path: <gcc-bugs-return-629943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42140 invoked by alias); 21 Jan 2019 09:20:42 -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 42045 invoked by uid 48); 21 Jan 2019 09:20:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88905] [8/9 Regression] ICE: in decompose, at rtl.h:2253 with -mabm and __builtin_popcountll
Date: Mon, 21 Jan 2019 09:20: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88905-4-ax9lJP4fWJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88905-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: 2019-01/txt/msg02752.txt.bz2
Content-length: 514

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Started with r254630 which is about a string warning. Martin, can you please
take a look what has changed with your revision?
>From gcc-bugs-return-629944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:21:22 2019
Return-Path: <gcc-bugs-return-629944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48232 invoked by alias); 21 Jan 2019 09:21:22 -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 48153 invoked by uid 48); 21 Jan 2019 09:21:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88925] address of static string changes
Date: Mon, 21 Jan 2019 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88925-4-uMj91YDZDj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88925-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88925-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: 2019-01/txt/msg02753.txt.bz2
Content-length: 300

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

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It works for me on x86_64-linux.  Note to get the desired behavior GCC relies
on
string-merging performed by the linker.

Can you elaborate on the host/target you compile for?
>From gcc-bugs-return-629945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:21:56 2019
Return-Path: <gcc-bugs-return-629945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49205 invoked by alias); 21 Jan 2019 09:21:56 -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 49139 invoked by uid 48); 21 Jan 2019 09:21:52 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88920-4-yFyBPRkxud@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02754.txt.bz2
Content-length: 292

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

--- Comment #5 from Andrew Stubbs <ams at gcc dot gnu.org> ---
The llvm_binutils check is needed because those tools emit blank lines all over
the place, so we end up with hundreds of stupid failures.

I'll look into caching it though.
>From gcc-bugs-return-629946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:22:18 2019
Return-Path: <gcc-bugs-return-629946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50038 invoked by alias); 21 Jan 2019 09:22:18 -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 49927 invoked by uid 48); 21 Jan 2019 09:22:10 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 09:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88920-4-Kvu5mCN4o3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02755.txt.bz2
Content-length: 374

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

Andrew Stubbs <ams at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |ams at gcc dot gnu.org
>From gcc-bugs-return-629947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:23:42 2019
Return-Path: <gcc-bugs-return-629947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51551 invoked by alias); 21 Jan 2019 09:23:41 -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 51454 invoked by uid 48); 21 Jan 2019 09:23:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 09:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-88934-4-KF0kE6GGdh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02756.txt.bz2
Content-length: 548

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org
   Target Milestone|---                         |9.0

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started to ICE with r260283 (though that change just adjusted checking), but I
can't reproduce it on current trunk.
>From gcc-bugs-return-629948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:25:52 2019
Return-Path: <gcc-bugs-return-629948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54646 invoked by alias); 21 Jan 2019 09:25:52 -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 54567 invoked by uid 48); 21 Jan 2019 09:25:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88926] ivopts with some NOP conversions
Date: Mon, 21 Jan 2019 09:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth 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: cf_gcctarget bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88926-4-cCSqlBbQuY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88926-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: 2019-01/txt/msg02757.txt.bz2
Content-length: 931

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-*
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
                 CC|                            |amker at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  Just to quote the testcase we don't optimize:

void
f1 (int *p, unsigned int i)
{
  __PTRDIFF_TYPE__ o = i;
  o *= 4;
  p = (int *)((char *)p + o);
  do
    {
      *p = 0;
      p += 1;
      i++;
    }
  while (i < 100);
}
>From gcc-bugs-return-629950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:26:18 2019
Return-Path: <gcc-bugs-return-629950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56246 invoked by alias); 21 Jan 2019 09:26:18 -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 56164 invoked by uid 48); 21 Jan 2019 09:26:14 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88934-4-Cfnyt4iEJ1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02759.txt.bz2
Content-length: 388

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

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Started to ICE with r260283 (though that change just adjusted checking), but
> I can't reproduce it on current trunk.

I can with r268110. Have you Jakub tried the original test-case or the reduced
one I provided?
>From gcc-bugs-return-629949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:26:05 2019
Return-Path: <gcc-bugs-return-629949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55436 invoked by alias); 21 Jan 2019 09:26:05 -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 55358 invoked by uid 48); 21 Jan 2019 09:26:01 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88922] Merge identical constants with different modes
Date: Mon, 21 Jan 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou 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:
Message-ID: <bug-88922-4-uDonaGsFyD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88922-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: 2019-01/txt/msg02758.txt.bz2
Content-length: 313

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

--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> IIRC I had patches to do this.  My main target was vector float constants vs
> scalar float constants.

OK, this particular case (scalar vs vector) would probably be worth the hassle.
>From gcc-bugs-return-629951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:27:12 2019
Return-Path: <gcc-bugs-return-629951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57469 invoked by alias); 21 Jan 2019 09:27:12 -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 57420 invoked by uid 48); 21 Jan 2019 09:27:07 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88939] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort
Date: Mon, 21 Jan 2019 09:27: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88939-4-sp0gpAHEZy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88939-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: 2019-01/txt/msg02760.txt.bz2
Content-length: 1799

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
The usual fix for this sort of problem is to move the map_pop to before the
GOMP_PLUGIN_fatal:
...
@@ -1365,6 +1365,7 @@ nvptx_exec
   if (async < acc_async_noval)
     {
       r = CUDA_CALL_NOCHECK (cuStreamSynchronize, dev_str->stream);
+      map_pop (dev_str);
       if (r == CUDA_ERROR_LAUNCH_FAILED)
        GOMP_PLUGIN_fatal ("cuStreamSynchronize error: %s %s\n", cuda_error
(r),
                           maybe_abort_msg);
@@ -1392,6 +1393,7 @@ nvptx_exec
     }
 #else
   r = CUDA_CALL_NOCHECK (cuCtxSynchronize, );
+  map_pop (dev_str);
   if (r == CUDA_ERROR_LAUNCH_FAILED)
     GOMP_PLUGIN_fatal ("cuCtxSynchronize error: %s %s\n", cuda_error (r),
                       maybe_abort_msg);
@@ -1401,11 +1403,6 @@ nvptx_exec

   GOMP_PLUGIN_debug (0, "  %s: kernel %s: finished\n", __FUNCTION__,
                     targ_fn->launch->fn);
-
-#ifndef DISABLE_ASYNC
-  if (async < acc_async_noval)
-#endif
-    map_pop (dev_str);
 }

 void * openacc_get_current_cuda_context (void);
...
but then we run into the same CUDA_ERROR_ILLEGAL_INSTRUCTION when calling
cuMemFree when trying to free the device pointer:
...
libgomp: cuStreamSynchronize error: an illegal instruction was encountered

libgomp: cuMemFree error: an illegal instruction was encountered
...
because the cuda error leaves the process in an inconsistent state and any
further CUDA calls in the process will return the same error:

We could do:
...
@@ -237,7 +237,7 @@ cuda_map_create (size_t size)
 static void
 cuda_map_destroy (struct cuda_map *map)
 {
-  CUDA_CALL_ASSERT (cuMemFree, map->d);
+  CUDA_CALL_NOCHECK (cuMemFree, map->d);
   free (map);
 }

...
but that's just a workaround.
>From gcc-bugs-return-629952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:27:25 2019
Return-Path: <gcc-bugs-return-629952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58268 invoked by alias); 21 Jan 2019 09:27:25 -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 58175 invoked by uid 48); 21 Jan 2019 09:27:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88920-4-1lzBG2Xnsh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02761.txt.bz2
Content-length: 308

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Emit blanks where?  On the stdout or stderr of the tool?
If so, wouldn't it be better to fix it, wrap them with a wrapper that would
remove that mess or change to a saner assembler/linker?
>From gcc-bugs-return-629953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:31:32 2019
Return-Path: <gcc-bugs-return-629953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69743 invoked by alias); 21 Jan 2019 09:31:32 -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 69263 invoked by uid 55); 21 Jan 2019 09:31:21 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88922] Merge identical constants with different modes
Date: Mon, 21 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
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:
Message-ID: <bug-88922-4-koQhSBTxTc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88922-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: 2019-01/txt/msg02762.txt.bz2
Content-length: 843

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

--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 21 Jan 2019, ebotcazou at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88922
> 
> --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> > IIRC I had patches to do this.  My main target was vector float constants vs
> > scalar float constants.
> 
> OK, this particular case (scalar vs vector) would probably be worth the hassle.

Yeah, saves some overhead from vectorization where also both variants
are usually accessed at the same time.  IIRC my implementation was
kind of a hack simply inserting additional constant descriptors for
element zero of a vector constant (and thus dependet on getting
the vector variant into the descriptor hash first...)
>From gcc-bugs-return-629954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:33:27 2019
Return-Path: <gcc-bugs-return-629954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83482 invoked by alias); 21 Jan 2019 09:33:26 -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 83409 invoked by uid 48); 21 Jan 2019 09:33:22 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Mon, 21 Jan 2019 09:33: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88928-4-ZiDdcQ95CR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg02763.txt.bz2
Content-length: 292

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
>From gcc-bugs-return-629955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:35:37 2019
Return-Path: <gcc-bugs-return-629955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8390 invoked by alias); 21 Jan 2019 09:35:37 -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 2681 invoked by uid 48); 21 Jan 2019 09:35:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88931] Failed to convert int128 to float/double with roundþ_UPWARD/FE_TOWARDZERO
Date: Mon, 21 Jan 2019 09:35: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88931-4-wlJlOfUgCo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88931-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: 2019-01/txt/msg02764.txt.bz2
Content-length: 186

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I guess it could, but then we do not fully support fenv access.
>From gcc-bugs-return-629956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:36:13 2019
Return-Path: <gcc-bugs-return-629956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10039 invoked by alias); 21 Jan 2019 09:36:13 -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 9938 invoked by uid 48); 21 Jan 2019 09:36:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88932] [8/9 Regression] ICE: verify_ssa failed (Error: definition in block 29 does not dominate use in block 25)
Date: Mon, 21 Jan 2019 09:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-88932-4-kESoylyobY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88932-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: 2019-01/txt/msg02765.txt.bz2
Content-length: 368

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
                 CC|                            |rguenth at gcc dot gnu.org
>From gcc-bugs-return-629957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:42:17 2019
Return-Path: <gcc-bugs-return-629957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57568 invoked by alias); 21 Jan 2019 09:42:17 -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 57507 invoked by uid 48); 21 Jan 2019 09:42:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 09:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status assigned_to
Message-ID: <bug-88936-4-uC283lEcFt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02766.txt.bz2
Content-length: 510

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-629958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:43:06 2019
Return-Path: <gcc-bugs-return-629958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59033 invoked by alias); 21 Jan 2019 09:43:06 -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 58962 invoked by uid 48); 21 Jan 2019 09:43:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 09:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88934-4-xh1NN02SUs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02767.txt.bz2
Content-length: 491

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look (can reproduce it).
>From gcc-bugs-return-629959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:53:34 2019
Return-Path: <gcc-bugs-return-629959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120384 invoked by alias); 21 Jan 2019 09:53:34 -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 120336 invoked by uid 48); 21 Jan 2019 09:53:26 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88939] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort
Date: Mon, 21 Jan 2019 09:53: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88939-4-g5kTCTK2bt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88939-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: 2019-01/txt/msg02768.txt.bz2
Content-length: 4583

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Furthermore, because of running into the cudaMemFree error, the process hangs
indefinitely with this callstack:
...
libgomp: cuStreamSynchronize error: an illegal instruction was encountered

libgomp: cuMemFree error: an illegal instruction was encountered
^C
Thread 1 "abort-1.exe" received signal SIGINT, Interrupt.
futex_wait (val=-1, addr=0x60ec28)
    at /home/vries/oacc/trunk/source-gcc/libgomp/config/linux/x86/futex.h:44
44        if (__builtin_expect (res == -ENOSYS, 0))
(gdb) bt
#0  futex_wait (val=-1, addr=0x60ec28)
    at /home/vries/oacc/trunk/source-gcc/libgomp/config/linux/x86/futex.h:44
#1  gomp_mutex_lock_slow (mutex=mutex@entry=0x60ec28, oldval=<optimized out>)
    at /home/vries/oacc/trunk/source-gcc/libgomp/config/linux/mutex.c:47
#2  0x00007ffff78baa90 in gomp_mutex_lock (mutex=0x60ec28)
    at /home/vries/oacc/trunk/source-gcc/libgomp/config/linux/mutex.h:57
#3  GOMP_offload_unregister_ver (version=<optimized out>, host_table=<optimized
out>, 
    target_type=<optimized out>, target_data=0x400cc0 <target_data>)
    at /home/vries/oacc/trunk/source-gcc/libgomp/target.c:1397
#4  0x000000000040084f in fini ()
#5  0x00007ffff7de7de7 in _dl_fini () at dl-fini.c:235
#6  0x00007ffff72e9ff8 in __run_exit_handlers (status=status@entry=1, 
    listp=0x7ffff76745f8 <__exit_funcs>,
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#7  0x00007ffff72ea045 in __GI_exit (status=status@entry=1) at exit.c:104
#8  0x00007ffff78a2b93 in gomp_vfatal (fmt=<optimized out>,
list=list@entry=0x7fffffffd668)
    at /home/vries/oacc/trunk/source-gcc/libgomp/error.c:80
#9  0x00007ffff78bcdfc in GOMP_PLUGIN_fatal (msg=msg@entry=0x7ffff6ea9953
"cuMemFree error: %s")
    at /home/vries/oacc/trunk/source-gcc/libgomp/libgomp-plugin.c:78
#10 0x00007ffff6ea63f2 in cuda_map_destroy (map=0xa2b4b0)
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:240
#11 0x00007ffff6ea6996 in map_fini (s=<optimized out>)
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:273
#12 0x00007ffff6ea807c in fini_streams_for_device (ptx_dev=0x60ea40)
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:503
#13 nvptx_close_device (ptx_dev=0x60ea40)
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:828
#14 GOMP_OFFLOAD_fini_device (n=<optimized out>)
---Type <return> to continue, or q <return> to quit---
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:1885
#15 0x00007ffff78b73a5 in gomp_target_fini ()
    at /home/vries/oacc/trunk/source-gcc/libgomp/target.c:2704
#16 0x00007ffff72e9ff8 in __run_exit_handlers (status=status@entry=1, 
    listp=0x7ffff76745f8 <__exit_funcs>,
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#17 0x00007ffff72ea045 in __GI_exit (status=status@entry=1) at exit.c:104
#18 0x00007ffff78a2b93 in gomp_vfatal (fmt=<optimized out>,
list=list@entry=0x7fffffffd838)
    at /home/vries/oacc/trunk/source-gcc/libgomp/error.c:80
#19 0x00007ffff78bcdfc in GOMP_PLUGIN_fatal (
    msg=msg@entry=0x7ffff6ea9af1 "cuStreamSynchronize error: %s")
    at /home/vries/oacc/trunk/source-gcc/libgomp/libgomp-plugin.c:78
#20 0x00007ffff6ea6f3c in nvptx_exec (fn=0xa574c0, mapnum=0,
devaddrs=<optimized out>, async=-2, 
    dims=0x7fffffffd9fc, targ_mem_desc=<optimized out>, hostaddrs=<optimized
out>)
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:1373
#21 0x00007ffff78bd1a9 in GOACC_parallel_keyed (flags_m=<optimized out>,
fn=<optimized out>, 
    mapnum=0, hostaddrs=0x0, sizes=<optimized out>, kinds=<optimized out>)
    at /home/vries/oacc/trunk/source-gcc/libgomp/oacc-parallel.c:249
#22 0x0000000000400784 in main ()
... 
The hang is due to &devicep->lock being locked twice, once in gomp_target_fini,
and once in GOMP_offload_unregister_ver.

Note btw that GOMP_PLUGIN_fatal calls exit, to allow the atexit handlers to
run, and that GOMP_PLUGIN_fatal is called in an exit handler, which calls exit
again. So, we're calling exit from an atexit handler. This is handled robustly
by glibc, so that as such doesn't cause the hang.

The hang is similar to what I described here (
http://gcc.gnu.org/ml/gcc-patches/2017-11/msg01444.html ), and the RFC patch
fixes the hang, as well as the cuMemFree error (though the patch may not be a
precise and minimal fix).
>From gcc-bugs-return-629960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 09:54:41 2019
Return-Path: <gcc-bugs-return-629960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6270 invoked by alias); 21 Jan 2019 09:54:41 -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 3168 invoked by uid 48); 21 Jan 2019 09:54:35 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 09:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88920-4-DqjZyk7ajM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02769.txt.bz2
Content-length: 483

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

--- Comment #7 from Andrew Stubbs <ams at gcc dot gnu.org> ---
I'm not sure that an assembler or linker can be labelled "insane" for choosing
to include some blank lines amongst its diagnostics. :-)

In any case, there's no other tool available, and no time/money available to
port Binutils at present, although I'd like to see that change.

I suppose we could add a wrapper, but would that really improve the user
experience?
>From gcc-bugs-return-629962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:09:34 2019
Return-Path: <gcc-bugs-return-629962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79227 invoked by alias); 21 Jan 2019 10:09:34 -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 77298 invoked by uid 48); 21 Jan 2019 10:09:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88920-4-cmq46JDCk5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02771.txt.bz2
Content-length: 679

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> Emit blanks where?  On the stdout or stderr of the tool?
> If so, wouldn't it be better to fix it, wrap them with a wrapper that would
> remove that mess or change to a saner assembler/linker?

First of all, I thought the current trunk amdgcn support is non-offloading
only, so you could at least for now always return 0 from
check_effective_target_offload_gcn, or am I wrong here?

Does the llvm as or ld emit blank lines even when not emitting any useful
diagnostics, or only if it emits some errors/warnings?
>From gcc-bugs-return-629961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:09:07 2019
Return-Path: <gcc-bugs-return-629961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65738 invoked by alias); 21 Jan 2019 10:09:07 -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 64439 invoked by uid 48); 21 Jan 2019 10:09:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88934-4-0U161ZVWBA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02770.txt.bz2
Content-length: 1053

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is we run into

static void
vect_get_constant_vectors (tree op, slp_tree slp_node,
                           vec<tree> *vec_oprnds,
                           unsigned int op_num, unsigned int number_of_vectors)
{
...
  /* Check if vector type is a boolean vector.  */
  if (VECT_SCALAR_BOOLEAN_TYPE_P (TREE_TYPE (op))
      && vect_mask_constant_operand_p (stmt_vinfo, op_num))
    vector_type
      = build_same_sized_truth_vector_type (STMT_VINFO_VECTYPE (stmt_vinfo));

for the pattern stmt patt_43 = _60 != 0 ? 1 : 0; when generating the constant
for != 0 which expects an unsigned 0 but gets a signed one.
vect_mask_constant_operand_p is quite useless here since for constants
'vectype' is never set to non-NULL.

The function is inconsistent in handling opnum for compare vs. cond and I
think it simply wants to look at the non-constant op (the first one).

The function is totally weird anyways...
>From gcc-bugs-return-629963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:27:28 2019
Return-Path: <gcc-bugs-return-629963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85261 invoked by alias); 21 Jan 2019 10:27:28 -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 79897 invoked by uid 48); 21 Jan 2019 10:27:23 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Mon, 21 Jan 2019 10:27: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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:
Message-ID: <bug-88906-4-s0XmYzp6mB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg02772.txt.bz2
Content-length: 573

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

--- Comment #5 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #4)
> Hard to bisect, because before r233979 this used to ICE or segfault in the
> compiler, starting with r201645 when -mmemcpy-strategy= option has been
> added, and already r233979 generates wrong-code.

Please see #3 comment. The RTL expansion of a memcpy does not mark pointers as
escaping. DSE1 pass later deduces that memory region, pointed by src pointer is
unused and removes its initialization.
>From gcc-bugs-return-629964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:31:58 2019
Return-Path: <gcc-bugs-return-629964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59520 invoked by alias); 21 Jan 2019 10:31:58 -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 59428 invoked by uid 48); 21 Jan 2019 10:31:52 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88920-4-cOtVJbHkBD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02773.txt.bz2
Content-length: 1454

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

--- Comment #9 from Andrew Stubbs <ams at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
> First of all, I thought the current trunk amdgcn support is non-offloading
> only, so you could at least for now always return 0 from
> check_effective_target_offload_gcn, or am I wrong here?

That's true, for now.

> Does the llvm as or ld emit blank lines even when not emitting any useful
> diagnostics, or only if it emits some errors/warnings?

Only when it emits diagnostics. For example:

.../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: open
>>> referenced by openr.c:50 (.../newlib/libc/reent/openr.c:50)
>>>               lib_a-openr.o:(_open_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a

.../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: open
>>> referenced by openr.c:50 (.../newlib/libc/reent/openr.c:50)
>>>               lib_a-openr.o:(_open_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a

.../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: kill
>>> referenced by signalr.c:53 (.../newlib/libc/reent/signalr.c:53)
>>>               lib_a-signalr.o:(_kill_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a

.../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: kill
>>> referenced by signalr.c:53 (.../newlib/libc/reent/signalr.c:53)
>>>               lib_a-signalr.o:(_kill_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a
>From gcc-bugs-return-629965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:32:39 2019
Return-Path: <gcc-bugs-return-629965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60498 invoked by alias); 21 Jan 2019 10:32:39 -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 60446 invoked by uid 48); 21 Jan 2019 10:32:34 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88940] New: [openacc, libgomp] cuModuleLoadData error for asynchronous parallel with abort
Date: Mon, 21 Jan 2019 10:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88940-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: 2019-01/txt/msg02774.txt.bz2
Content-length: 3221

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

            Bug ID: 88940
           Summary: [openacc, libgomp] cuModuleLoadData error for
                    asynchronous parallel with abort
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider abort-6.c (the async version of abort-1.c):
...
/* { dg-do run } */

#include <stdio.h>
#include <stdlib.h>

int
main (void)
{
  fprintf (stderr, "CheCKpOInT\n");
#pragma acc parallel async
  {
    abort ();
  }

  #pragma acc wait
  return 0;
}

/* { dg-output "CheCKpOInT" } */
/* { dg-shouldfail ""  } */
...

It passes at O2 like this:
...
CheCKpOInT

libgomp: cuModuleLoadData error: an illegal instruction was encountered

libgomp: Cannot map target functions or variables (expected 1, have 4294967295)
PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/abort-6.c \ 
  -DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0  -O2  execution test
...

Normally, the compiler can optimize away the code following an abort, because
the abort is a noreturn call.

In the case of an async parallel however, the parallel region is executed
asynchronously, that is, the expected behaviour is:
- the kernel representing the parallel region is launched
- the code launching the kernel does not wait for the launch to start or
finish,
- the code following the parallel region is executed

So, in the case of the test-case above, we can eliminate all code after the
abort inside the parallel async region, but we can't eliminated any code after
the parallel async region.

The compiler presently does precisely that: it removes the code after the
parallel async region. At eh, we have:
...
main ()
{
  int D.3104;

  stderr.0_1 = stderr;
  __builtin_fwrite ("CheCKpOInT\n", 1, 11, stderr.0_1);
  #pragma omp target oacc_parallel async(-1) [child fn: main._omp_fn.0 (???)]
  abort ();
  #pragma omp return
  __builtin_GOACC_wait (-2, 0);
  D.3104 = 0;
  goto <D.3109>;
  D.3104 = 0;
  goto <D.3109>;
  <D.3109>:
  return D.3104;
}
...

and at cfg, we have:
...
main ()
{
  int D.3104;

  <bb 2> :
  stderr.0_1 = stderr;
  __builtin_fwrite ("CheCKpOInT\n", 1, 11, stderr.0_1);
  #pragma omp target oacc_parallel async(-1) [child fn: main._omp_fn.0 (???)]   

  <bb 3> :
  abort ();

}
...

And at optimized:
...
main ()
{
  struct _IO_FILE * stderr.0_1;

  <bb 2> [local count: 1073741824]:
  stderr.0_1 = stderr;
  fwrite ("CheCKpOInT\n", 1, 11, stderr.0_1);
  GOACC_parallel_keyed (-1, main._omp_fn.0, 0, 0B, 0B, 0B, 536936447, -1, 0);
  __builtin_unreachable ();

}
...

The __builtin_unreachable seems to expand to nothing, so at runtime, when
executing main, we return from GOACC_parallel_keyed, step out of main, and
start executing the code after main, which happens to be _start, which
eventually leads to cuModuleLoadData picking up the result of the abort, which
leads to the "Cannot map" error message.

This problem is encountered for the nvptx target, but I think this is a generic
openacc problem.
>From gcc-bugs-return-629966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:35:31 2019
Return-Path: <gcc-bugs-return-629966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64393 invoked by alias); 21 Jan 2019 10:35:31 -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 64322 invoked by uid 48); 21 Jan 2019 10:35:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 10:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88936-4-XVpMESs242@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02775.txt.bz2
Content-length: 1511

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, so the issue is that the clobber of rD.1909 makes *v_8(D) = 0 dead
because IPA points-to uses the callers r UID in the points-to set on
the receiving side as well.

bug (long intD.8 depthD.1905, long intD.8 * vD.1906)
{
  # RANGE [-9223372036854775808, 9223372036854775806]
  long intD.8 depth_6(D) = depthD.1905;
  # PT = null { D.1909 }
  # ALIGN = 8, MISALIGN = 0
  long intD.8 * v_8(D) = vD.1906;
  long intD.8 valD.1910;
...
  <bb 2> [local count: 1073741824]:
  if (depth_6(D) == 0)
    goto <bb 3>; [51.12%]
  else
    goto <bb 4>; [48.88%]

  <bb 3> [local count: 548896821]:
  *v_8(D) = 0;
  goto <bb 5>; [100.00%]
...
  <bb 5> [local count: 1073741824]:
  # _4 = PHI <1(3), _13(4)>
  rD.1909 ={v} {CLOBBER};
  return _4;

}


I don't see an easy way to mitigate this (this can also happen in arbitrary
cycles).  We have to support the case where exactly this UID needs to be
present (if a pointer to r is returned again) as well as the case of
supporting alternate instantiations of r.  One way would be to always
pass down another dummy var (but we'd need a UID for that).  There's
also the missed optimization that bug() doesn't know v does not point
to its local r in IPA-PTA (I think).

Cycles are difficult.

A simple approach might be to drop to non-IPA mode for members of a
cgraph cycle.  Do we have an utility to compute SCCs of the callgraph?
>From gcc-bugs-return-629967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:36:22 2019
Return-Path: <gcc-bugs-return-629967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66127 invoked by alias); 21 Jan 2019 10:36:22 -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 65718 invoked by uid 48); 21 Jan 2019 10:36:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 10:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88920-4-ULpMAvKfB5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02776.txt.bz2
Content-length: 1439

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Stubbs from comment #9)
> > Does the llvm as or ld emit blank lines even when not emitting any useful
> > diagnostics, or only if it emits some errors/warnings?
> 
> Only when it emits diagnostics. For example:
> 
> .../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: open
> >>> referenced by openr.c:50 (.../newlib/libc/reent/openr.c:50)
> >>>               lib_a-openr.o:(_open_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a
> 
> .../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: open
> >>> referenced by openr.c:50 (.../newlib/libc/reent/openr.c:50)
> >>>               lib_a-openr.o:(_open_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a
> 
> .../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: kill
> >>> referenced by signalr.c:53 (.../newlib/libc/reent/signalr.c:53)
> >>>               lib_a-signalr.o:(_kill_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a
> 
> .../amdgcn-unknown-amdhsa/bin/ld: error: undefined symbol: kill
> >>> referenced by signalr.c:53 (.../newlib/libc/reent/signalr.c:53)
> >>>               lib_a-signalr.o:(_kill_r) in archive .../amdgcn-unknown-amdhsa/lib/libc.a

But then it should affect only testcases that FAIL already for other reasons.
And when the issue is fixed, these extra errors would go away too.
>From gcc-bugs-return-629968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:51:37 2019
Return-Path: <gcc-bugs-return-629968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125525 invoked by alias); 21 Jan 2019 10:51:37 -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 125443 invoked by uid 48); 21 Jan 2019 10:51:32 -0000
From: "csaba_22 at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88263] ICE in coverage_begin_function
Date: Mon, 21 Jan 2019 10:51: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: csaba_22 at yahoo dot co.uk
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88263-4-dw7X7FRgDi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88263-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: 2019-01/txt/msg02777.txt.bz2
Content-length: 226

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

--- Comment #9 from Csaba RÃ¡duly <csaba_22 at yahoo dot co.uk> ---
Confirmed. The original logger.cc (from which logger2.cc was derived) is now
compiled successfully.
>From gcc-bugs-return-629969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 10:57:58 2019
Return-Path: <gcc-bugs-return-629969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34862 invoked by alias); 21 Jan 2019 10:57:58 -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 34807 invoked by uid 48); 21 Jan 2019 10:57:54 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] ICE in extract_insn, at recog.c:2304
Date: Mon, 21 Jan 2019 10:57: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88938-4-YIEdXjb0tN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88938-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: 2019-01/txt/msg02778.txt.bz2
Content-length: 581

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1

--- Comment #1 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Operand sanitization for IX86_BUILTIN_BEXTRI32 and IX86_BUILTIN_BEXTRI64 is
missing in ix86_expand_builtin.
>From gcc-bugs-return-629970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:01:07 2019
Return-Path: <gcc-bugs-return-629970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41902 invoked by alias); 21 Jan 2019 11:01:05 -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 41345 invoked by uid 48); 21 Jan 2019 11:00:50 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/88941] New: [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel
Date: Mon, 21 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88941-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: 2019-01/txt/msg02779.txt.bz2
Content-length: 1706

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

            Bug ID: 88941
           Summary: [nvptx, openacc, libgomp] Assertion `!s->map->active'
                    failed for empty asynchronous parallel
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org
  Target Milestone: ---

Consider test-case:
...
$ cat libgomp/testsuite/libgomp.oacc-c-c++-common/empty-async.c
/* { dg-do run } */

#include <stdlib.h>

int
main (void)
{

#pragma acc parallel async
  ;

  /* no #pragma acc wait */
  return 0;
}
...

It fails in execution:
...
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/empty-async.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0  -O0  execution test
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/empty-async.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0  -O2  execution test
...

because:
...
empty-async.exe: libgomp/plugin/plugin-nvptx.c:271: map_fini: Assertion
`!s->map->active' failed.
...

The following scenario happens:
- map_push allocates a struct cuda_map for the kernel launch parameters
- the kernel is launched
- an event is registered to call the corresponding map_pop after the kernel
  completes
- main reaches return, and atexit processing starts
- during atexit processing, fini_streams_for_device is called, which calls
  map_fini
- map_fini asserts, because map_pop hasn't been called.

So either:
- the kernel hasn't finished yet, or
- the kernel has finished, but the event has not been processed
>From gcc-bugs-return-629971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:04:27 2019
Return-Path: <gcc-bugs-return-629971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58425 invoked by alias); 21 Jan 2019 11:04:26 -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 54427 invoked by uid 48); 21 Jan 2019 11:04:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70480] Reduce RTTI code bloat for specified types
Date: Mon, 21 Jan 2019 11:04: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: 5.3.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-70480-4-AXPUiJM8cc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70480-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70480-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: 2019-01/txt/msg02780.txt.bz2
Content-length: 402

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1
>From gcc-bugs-return-629972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:09:44 2019
Return-Path: <gcc-bugs-return-629972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124978 invoked by alias); 21 Jan 2019 11:09:44 -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 124916 invoked by uid 48); 21 Jan 2019 11:09:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88501] Improve suggested alternative to be closer to typo
Date: Mon, 21 Jan 2019 11:09: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: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88501-4-mGgfNwLW5s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88501-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88501-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: 2019-01/txt/msg02781.txt.bz2
Content-length: 186

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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's only relevant for C, not C++, so should be a separate bug.
>From gcc-bugs-return-629973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:12:19 2019
Return-Path: <gcc-bugs-return-629973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128494 invoked by alias); 21 Jan 2019 11:12:19 -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 128019 invoked by uid 48); 21 Jan 2019 11:12:10 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38182] stddef.h assumes machinee/ansi.h defines _ANSI_H_
Date: Mon, 21 Jan 2019 11:12: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: 4.4.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-38182-4-gItbGmMCoJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38182-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38182-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: 2019-01/txt/msg02782.txt.bz2
Content-length: 175

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

--- Comment #19 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Is it even still an issue? I think NetBSD builds now.
>From gcc-bugs-return-629974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:19:09 2019
Return-Path: <gcc-bugs-return-629974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17122 invoked by alias); 21 Jan 2019 11:19:09 -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 17035 invoked by uid 48); 21 Jan 2019 11:19:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88936-4-QPTWxb5Fif@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02783.txt.bz2
Content-length: 592

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Honza, is there a way to get at "is this cgraph edge inside a cycle"?  I can
of course compute SCCs myself (pushing the cgraph to graphds for example),
but IIRC some IPA code already computes cgraph cycles.
>From gcc-bugs-return-629975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:21:06 2019
Return-Path: <gcc-bugs-return-629975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26853 invoked by alias); 21 Jan 2019 11:21:05 -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 26188 invoked by uid 48); 21 Jan 2019 11:20:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Mon, 21 Jan 2019 11:21: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: attachments.created
Message-ID: <bug-88906-4-nqfHTtH8b7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg02784.txt.bz2
Content-length: 253

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45477
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45477&action=edit
gcc9-pr88906.patch

Untested fix.
>From gcc-bugs-return-629976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:23:57 2019
Return-Path: <gcc-bugs-return-629976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33991 invoked by alias); 21 Jan 2019 11:23:57 -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 33974 invoked by uid 89); 21 Jan 2019 11:23:56 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.8 required=5.0 testsºYES_50,HTML_MESSAGE,SPF_FAIL autolearn=no version=3.3.2 spammy=CLICK, H*r:sk:correo., H*RU:sk:correo., Hx-spam-relays-external:sk:correo.
X-HELO: correo.mindefensa.gob.ve
Received: from Unknown (HELO correo.mindefensa.gob.ve) (200.109.228.8) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 21 Jan 2019 11:23:54 +0000
Received: from localhost (localhost [127.0.0.1])	by correo.mindefensa.gob.ve (Postfix) with ESMTP id D8AFF3668064	for <gcc-bugs@gcc.gnu.org>; Mon, 21 Jan 2019 07:05:45 -0400 (-04)
Received: from correo.mindefensa.gob.ve ([127.0.0.1])	by localhost (correo.mindefensa.gob.ve [127.0.0.1]) (amavisd-new, port 10032)	with ESMTP id WzXGSNigtJUQ for <gcc-bugs@gcc.gnu.org>;	Mon, 21 Jan 2019 07:05:45 -0400 (-04)
Received: from localhost (localhost [127.0.0.1])	by correo.mindefensa.gob.ve (Postfix) with ESMTP id B86A8366AF87	for <gcc-bugs@gcc.gnu.org>; Mon, 21 Jan 2019 06:32:32 -0400 (-04)
Received: from correo.mindefensa.gob.ve ([127.0.0.1])	by localhost (correo.mindefensa.gob.ve [127.0.0.1]) (amavisd-new, port 10026)	with ESMTP id C_VfY-6n3A_R for <gcc-bugs@gcc.gnu.org>;	Mon, 21 Jan 2019 06:32:32 -0400 (-04)
Received: from rdpp.lbjfsv11b25ubdk2obws1ui2hc.qx.internal.cloudapp.net (unknown [52.189.192.80])	by correo.mindefensa.gob.ve (Postfix) with ESMTPSA id B7C14365EF6B	for <gcc-bugs@gcc.gnu.org>; Mon, 21 Jan 2019 05:56:07 -0400 (-04)
MIME-Version: 1.0
Subject: email update for gcc-bugs@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "Zimbra Help Desk via gcc-bugs" <gcc-bugs@gcc.gnu.org>
Reply-To: "Zimbra Help Desk" <helpdesks.zimbras@zimbra.com>
Date: Mon, 21 Jan 2019 11:23:00 -0000
Message-Id: <20190121095608.B7C14365EF6B@correo.mindefensa.gob.ve>
Content-Description: Mail message body
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2019-01/txt/msg02785.txt.bz2
Content-length: 305

This is to inform you that we will be undergoing system upgrade/maintenance of our systems between 10pm-11pm today.As a result you will be required to verify your email by CLICK HERE in order for us to upgrade your Zimbra account. Once again we are sorry for any inconveniences this might cause you
>From gcc-bugs-return-629977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:41:13 2019
Return-Path: <gcc-bugs-return-629977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92976 invoked by alias); 21 Jan 2019 11:41:13 -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 92568 invoked by uid 48); 21 Jan 2019 11:41:07 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/88941] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel
Date: Mon, 21 Jan 2019 11:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88941-4-WB0D9cK0FQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88941-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: 2019-01/txt/msg02786.txt.bz2
Content-length: 2515

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
A patch like this waits for the kernel to finish, and then forces processing
the event, so it fixes the failing test-case:
...
diff --git a/libgomp/plugin/plugin-nvptx.c b/libgomp/plugin/plugin-nvptx.c
index dd2bcf3083f..56334a401dc 100644
--- a/libgomp/plugin/plugin-nvptx.c
+++ b/libgomp/plugin/plugin-nvptx.c
@@ -478,6 +478,8 @@ init_streams_for_device (struct ptx_device *ptx_dev, int
concurrency)
   return true;
 }

+static void event_gc (bool);
+
 static bool
 fini_streams_for_device (struct ptx_device *ptx_dev)
 {
@@ -489,6 +491,8 @@ fini_streams_for_device (struct ptx_device *ptx_dev)
       struct ptx_stream *s = ptx_dev->active_streams;
       ptx_dev->active_streams = ptx_dev->active_streams->next;

+      CUDA_CALL_ASSERT (cuStreamSynchronize, s->stream);
+      event_gc (false);
       ret &= map_fini (s);

       CUresult r = CUDA_CALL_NOCHECK (cuStreamDestroy, s->stream);
...

but, it causes a regression for lib-82.c. There's a segfault in the event_gc we
just added, because nvthd is NULL, and we dereferencing it here:
...
1029          if (e->ord != nvthd->ptx_dev->ord)
1030            continue;
(gdb) p nvthd
$9 = (struct nvptx_thread *) 0x0
...

The nvthd is NULL, because at that point the acc_shutdown (in the lib-82.c
source) has resulted in calling GOMP_OFFLOAD_openacc_destroy_thread_data.

At the acc_shutdown documentation, we read:
..
- This routine may not be called during execution of an accelerator compute
  region.
- If the program attempts to execute a compute region or access any device
  data on such a device, the behavior is undefined.
...

The lib-82.c testcase launches kernels asynchronously (not by using parallel
async, but by using cuLaunchKernel).

The documentation of acc_shutdown seems to imply that we need to wait for all
those streams finish before calling acc_shutdown.

There is a wait call before acc_shutdown:
...
  acc_wait_all_async (0);
...
but the semantics for that one is:
...
The acc_wait_all_async routine enqueues wait operations on one async queue
for the operations previously enqueued on all other async queues.
...

ISTM that this can't guarantee that all queues have finished.

OTOH, using acc_wait_all, with semantics:
...
The acc_wait_all routine waits for completion of all asynchronous operations.
...
seems to guarantee that, and indeed using this call instead fixed the lib-82.c
failure.
>From gcc-bugs-return-629978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:45:45 2019
Return-Path: <gcc-bugs-return-629978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97867 invoked by alias); 21 Jan 2019 11:45:44 -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 97614 invoked by uid 48); 21 Jan 2019 11:45:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Mon, 21 Jan 2019 11:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88927-4-6UYRGviAkw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02787.txt.bz2
Content-length: 696

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The #c2 change looks good to me, allowed armv7hl to bootstrap and compared to
8.2.1 from a week ago the libgo/gotools difference is
-FAIL: io
-FAIL: log
+FAIL: fmt
+FAIL: go/constant
+FAIL: html/template
+FAIL: math/big
+FAIL: net/rpc
 FAIL: runtime
-FAIL: os/signal
 FAIL: runtime/pprof
+FAIL: sync
 FAIL: sync/atomic
+FAIL: text/template
+FAIL: text/template/parse

and
 FAIL: go test runtime
+FAIL: go test misc/cgo/test
 FAIL: TestEarlySignalHandler
 FAIL: go test misc/cgo/testcarchive
+FAIL: TestVet
+FAIL: go test cmd/vet

s390x libgo is in much worse shape it seems.
>From gcc-bugs-return-629979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:49:12 2019
Return-Path: <gcc-bugs-return-629979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108184 invoked by alias); 21 Jan 2019 11:49:12 -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 108091 invoked by uid 48); 21 Jan 2019 11:49:07 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88942] New: [openacc, testsuite] lib-82.c does not wait for all streams before calling acc_shutdown
Date: Mon, 21 Jan 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88942-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: 2019-01/txt/msg02788.txt.bz2
Content-length: 1860

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

            Bug ID: 88942
           Summary: [openacc, testsuite] lib-82.c does not wait for all
                    streams before calling acc_shutdown
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

[ Spin-off bug from PR88941 - "[nvptx, openacc, libgomp] Assertion
`!s->map->active' failed for empty asynchronous parallel" ]

In lib-82.c, we have:
...
  acc_wait_all_async (0);

  ...

  acc_shutdown (acc_device_nvidia);
...

At the acc_shutdown documentation, we read:
..
- This routine may not be called during execution of an accelerator compute
  region.
- If the program attempts to execute a compute region or access any device
  data on such a device, the behavior is undefined.
...

The lib-82.c testcase launches kernels asynchronously (not by using parallel
async, but by using cuLaunchKernel).

The documentation of acc_shutdown seems to imply that we need to wait for all
those streams to finish before calling acc_shutdown.

There is a wait call before acc_shutdown:
...
  acc_wait_all_async (0);
...
but the semantics for that one is:
...
The acc_wait_all_async routine enqueues wait operations on one async queue
for the operations previously enqueued on all other async queues.
...

ISTM that this can't guarantee that all queues have finished.

OTOH, using acc_wait_all, with semantics:
...
The acc_wait_all routine waits for completion of all asynchronous operations.
...
seems to guarantee that.

We should fix the test-case.

[ It would be nice have a warning or error for this, that is, when calling
shutdown, to report on unfinished stream. ]
>From gcc-bugs-return-629980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:51:43 2019
Return-Path: <gcc-bugs-return-629980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113435 invoked by alias); 21 Jan 2019 11:51:43 -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 113356 invoked by uid 48); 21 Jan 2019 11:51:39 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88942] [openacc, testsuite] lib-82.c does not wait for all streams before calling acc_shutdown
Date: Mon, 21 Jan 2019 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords cc
Message-ID: <bug-88942-4-Qox7xbzFsd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88942-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88942-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: 2019-01/txt/msg02789.txt.bz2
Content-length: 548

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |openacc
                 CC|                            |tschwinge at gcc dot gnu.org

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Thomas, do you agree with the assessment that lib-82.c in its current form is
an invalid openacc test-case?
>From gcc-bugs-return-629981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:53:32 2019
Return-Path: <gcc-bugs-return-629981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115540 invoked by alias); 21 Jan 2019 11:53:31 -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 115486 invoked by uid 48); 21 Jan 2019 11:53:27 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/88941] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel
Date: Mon, 21 Jan 2019 11:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88941-4-JkUAyni8cP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88941-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: 2019-01/txt/msg02790.txt.bz2
Content-length: 1402

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> At the acc_shutdown documentation, we read:
> ..
> - This routine may not be called during execution of an accelerator compute
>   region.
> - If the program attempts to execute a compute region or access any device
>   data on such a device, the behavior is undefined.
> ...
> 
> The lib-82.c testcase launches kernels asynchronously (not by using parallel
> async, but by using cuLaunchKernel).
> 
> The documentation of acc_shutdown seems to imply that we need to wait for
> all those streams finish before calling acc_shutdown.
> 
> There is a wait call before acc_shutdown:
> ...
>   acc_wait_all_async (0);
> ...
> but the semantics for that one is:
> ...
> The acc_wait_all_async routine enqueues wait operations on one async queue
> for the operations previously enqueued on all other async queues.
> ...
> 
> ISTM that this can't guarantee that all queues have finished.
> 
> OTOH, using acc_wait_all, with semantics:
> ...
> The acc_wait_all routine waits for completion of all asynchronous operations.
> ...
> seems to guarantee that, and indeed using this call instead fixed the
> lib-82.c failure.

Filed as PR88942 - "[openacc, testsuite] lib-82.c does not wait for all streams
before calling acc_shutdown"
>From gcc-bugs-return-629982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:54:51 2019
Return-Path: <gcc-bugs-return-629982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117449 invoked by alias); 21 Jan 2019 11:54:51 -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 117383 invoked by uid 48); 21 Jan 2019 11:54:47 -0000
From: "alex at jakalx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/88943] New: Compiler switch -gnatceg does not generate C headers
Date: Mon, 21 Jan 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: alex at jakalx dot net
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88943-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: 2019-01/txt/msg02791.txt.bz2
Content-length: 880

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

            Bug ID: 88943
           Summary: Compiler switch -gnatceg does not generate C headers
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
          Assignee: unassigned at gcc dot gnu.org
          Reporter: alex at jakalx dot net
  Target Milestone: ---

Running the following example does not generate the corresponding header file
according to the documentation (3.11.5.1).

-- foo.ads
package foo is
  type bar is record
     I : Integer;
  end record;
end;

$ gcc -c -gnatceg foo.ads

Looking into the generated .ali file, it seems that the switch gets parsed into
-gnatc and -gnateg:

---
A -gnatc
A -gnateg
A -mtune=generic
A -march=x86-64
---

Am I doing something stupid?

Best regards,
Alex
>From gcc-bugs-return-629983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 11:56:32 2019
Return-Path: <gcc-bugs-return-629983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120335 invoked by alias); 21 Jan 2019 11:56:31 -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 120224 invoked by uid 55); 21 Jan 2019 11:56:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86590] Codegen is poor when passing std::string by value with _GLIBCXX_EXTERN_TEMPLATE undefined
Date: Mon, 21 Jan 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86590-4-VFsuYRXTk8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86590-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86590-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: 2019-01/txt/msg02792.txt.bz2
Content-length: 532

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

--- Comment #32 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 21 11:55:52 2019
New Revision: 268112

URL: https://gcc.gnu.org/viewcvs?rev=268112&root=gcc&view=rev
Log:
        PR libstdc++/86590
        * include/bits/char_traits.h (__constant_string_p,
        __constant_char_array_p): Use __builtin_is_constant_evaluated if
        available.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/include/bits/char_traits.h
>From gcc-bugs-return-629984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:05:34 2019
Return-Path: <gcc-bugs-return-629984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48016 invoked by alias); 21 Jan 2019 12:05:34 -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 47862 invoked by uid 48); 21 Jan 2019 12:05:27 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] ICE in extract_insn, at recog.c:2304
Date: Mon, 21 Jan 2019 12:05: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to target_milestone
Message-ID: <bug-88938-4-urpXSh3oXd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88938-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: 2019-01/txt/msg02793.txt.bz2
Content-length: 1395

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |ubizjak at gmail dot com
   Target Milestone|---                         |7.5

--- Comment #2 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Patch in testing:

--cut here--
diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
index 8abff99cc626..88557f26c44c 100644
--- a/gcc/config/i386/i386.c
+++ b/gcc/config/i386/i386.c
@@ -37215,6 +37215,16 @@ ix86_expand_builtin (tree exp, rtx target, rtx
subtarget,
           unsigned char lsb_index = INTVAL (op1) & 0xFF;
           op1 = GEN_INT (length);
           op2 = GEN_INT (lsb_index);
+
+         mode1 = insn_data[icode].operand[1].mode;
+         if (!insn_data[icode].operand[1].predicate (op0, mode1))
+           op0 = copy_to_mode_reg (mode1, op0);
+
+         mode0 = insn_data[icode].operand[0].mode;
+         if (target == 0
+             || !register_operand (target, mode0))
+           target = gen_reg_rtx (mode0);
+
           pat = GEN_FCN (icode) (target, op0, op1, op2);
           if (pat)
             emit_insn (pat);
--cut here--
>From gcc-bugs-return-629985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:18:10 2019
Return-Path: <gcc-bugs-return-629985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87352 invoked by alias); 21 Jan 2019 12:18: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 87278 invoked by uid 48); 21 Jan 2019 12:18:06 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Mon, 21 Jan 2019 12:18: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88877-4-3G1mRtjIze@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg02794.txt.bz2
Content-length: 222

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

--- Comment #16 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Is anything broken though?

If the libcall routines know they are called this way, all is fine.
>From gcc-bugs-return-629986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:19:45 2019
Return-Path: <gcc-bugs-return-629986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91398 invoked by alias); 21 Jan 2019 12:19:45 -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 91353 invoked by uid 48); 21 Jan 2019 12:19:40 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88944] New: Suggested alternative C stdbool.h
Date: Mon, 21 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88944-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: 2019-01/txt/msg02795.txt.bz2
Content-length: 4013

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

            Bug ID: 88944
           Summary: Suggested alternative C stdbool.h
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jg at jguk dot org
  Target Milestone: ---

Created attachment 45478
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45478&action=edit
testcase

Would be good if GCC could suggest <stdbool.h>

$ gcc -o undef undef.c
undef.c: In function â€˜mainâ€™:
undef.c:4:5: error: unknown type name â€˜boolâ€™; did you mean â€˜_Boolâ€™?
     bool a;
     ^~~~
     _Bool




int main ()
{
    bool a;
    a = 98;
    return 0;
}




$ gcc-8 -v -save-temps undef2.c
Using built-in specs.
COLLECT_GCC=gcc-8
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-1ubuntu2~18.04' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-1ubuntu2~18.04) 
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-mtune=generic' '-march=x86-64'
 /usr/lib/gcc/x86_64-linux-gnu/8/cc1 -E -quiet -v -imultiarch x86_64-linux-gnu
undef2.c -mtune=generic -march=x86-64 -fpch-preprocess -fstack-protector-strong
-Wformat -Wformat-security -o undef2.i
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-linux-gnu/8/../../../../x86_64-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/lib/gcc/x86_64-linux-gnu/8/include
 /usr/local/include
 /usr/lib/gcc/x86_64-linux-gnu/8/include-fixed
 /usr/include/x86_64-linux-gnu
 /usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-mtune=generic' '-march=x86-64'
 /usr/lib/gcc/x86_64-linux-gnu/8/cc1 -fpreprocessed undef2.i -quiet -dumpbase
undef2.c -mtune=generic -march=x86-64 -auxbase undef2 -version
-fstack-protector-strong -Wformat -Wformat-security -o undef2.s
GNU C17 (Ubuntu 8.2.0-1ubuntu2~18.04) version 8.2.0 (x86_64-linux-gnu)
        compiled by GNU C version 8.2.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C17 (Ubuntu 8.2.0-1ubuntu2~18.04) version 8.2.0 (x86_64-linux-gnu)
        compiled by GNU C version 8.2.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 465f91519bea3044f6e4e12330b25007
undef2.c: In function â€˜mainâ€™:
undef2.c:4:5: error: unknown type name â€˜boolâ€™; did you mean â€˜_Boolâ€™?
     bool a;
     ^~~~
     _Bool
>From gcc-bugs-return-629987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:22:33 2019
Return-Path: <gcc-bugs-return-629987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96635 invoked by alias); 21 Jan 2019 12:22:32 -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 96304 invoked by uid 48); 21 Jan 2019 12:22:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88945] New: ICE in fold_convert_loc in FRE when using -fdump-tree-fre-details
Date: Mon, 21 Jan 2019 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88945-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: 2019-01/txt/msg02796.txt.bz2
Content-length: 6366

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

            Bug ID: 88945
           Summary: ICE in fold_convert_loc in FRE when using
                    -fdump-tree-fre-details
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: rguenth at gcc dot gnu.org
  Target Milestone: ---

It's probably an older issue, but was exposed in r257233:

$ cat /tmp/task2.f90
  call a
contains
  subroutine b (c, d, e, f, g, h, i, j, k, l)
    character  c
    character  d
    integer, dimension (l) :: e
    integer, dimension (l) :: f
    character (*), dimension (l) :: g
    character  h
    real, dimension (:, :, :) :: i
    double precision, dimension (:, :, :) :: j
    integer, dimension (:, :, :) :: k
  g = ''
  end  
  subroutine a
    character  c
    character  d
    integer, dimension (7) :: e
    integer, dimension (7) :: f
    character g
    character h
    real, dimension (5, 6, 7) :: i
    double precision, dimension (6, 6, 7) :: j
    integer, dimension (5, 7, 6) :: k
    call b (c, d, e, f, g, h, i, j, k, 7)
  end  
end

$ ./xgcc -B. /tmp/task2.f90 -c -O -fdump-tree-fre-details
during GIMPLE pass: fre
dump file: task2.f90.033t.fre1
xgcc: internal compiler error: Segmentation fault signal terminated program
f951
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.

Program received signal SIGSEGV, Segmentation fault.
0x0000000000ab00c2 in fold_convert_loc (loc=49248, type=<integer_type
0x7ffff6b68000 sizetype>, arg=<ssa_name 0x7ffff6d41048>) at
/home/marxin/Programming/gcc/gcc/fold-const.c:2400
2400          || TREE_CODE (orig) == ERROR_MARK)
(gdb) bt
#0  0x0000000000ab00c2 in fold_convert_loc (loc=49248, type=<integer_type
0x7ffff6b68000 sizetype>, arg=<ssa_name 0x7ffff6d41048>) at
/home/marxin/Programming/gcc/gcc/fold-const.c:2400
#1  0x000000000105e12c in array_ref_element_size (exp=<optimized out>) at
/home/marxin/Programming/gcc/gcc/tree.c:13462
#2  0x0000000000e7a295 in dump_generic_node (pp=0x7fffffffd500, node=<array_ref
0x7ffff6b5cf88>, spc=0, flags=TDF_BLOCKS, is_stmt=<optimized out>) at
/home/marxin/Programming/gcc/gcc/tree-pretty-print.c:2154
#3  0x0000000000e7e656 in dump_generic_node (pp=pp@entry=0x7fffffffd500,
node=<addr_expr 0x7ffff6d33880>, spc=spc@entry=0, flags=flags@entry=TDF_BLOCKS,
is_stmt=is_stmt@entry=false) at
/home/marxin/Programming/gcc/gcc/tree-pretty-print.c:2586
#4  0x0000000000b374bd in dump_unary_rhs (flags=TDF_BLOCKS, spc=0,
gs=<optimized out>, buffer=0x7fffffffd500) at
/home/marxin/Programming/gcc/gcc/gimple-pretty-print.c:408
#5  dump_gimple_assign (buffer=0x7fffffffd500, gs=<optimized out>, spc=0,
flags=TDF_BLOCKS) at /home/marxin/Programming/gcc/gcc/gimple-pretty-print.c:628
#6  0x0000000000b38d6a in gimple_dump_bb_buff (flags=TDF_BLOCKS, indent=0,
bb=<basic_block 0x7ffff6b5b888 (7)>, buffer=0x7fffffffd500) at
/home/marxin/Programming/gcc/gcc/gimple-pretty-print.c:2854
#7  gimple_dump_bb (file=<optimized out>, bb=<basic_block 0x7ffff6b5b888 (7)>,
indent=0, flags=TDF_BLOCKS) at
/home/marxin/Programming/gcc/gcc/gimple-pretty-print.c:2878
#8  0x0000000000979eb5 in dump_bb (outf=0x232dd50, bb=bb@entry=<basic_block
0x7ffff6b5b888 (7)>, indent=indent@entry=0, flags=flags@entry=TDF_BLOCKS) at
/home/marxin/Programming/gcc/gcc/cfghooks.c:282
#9  0x0000000000def2b6 in remove_bb (bb=<basic_block 0x7ffff6b5b888 (7)>) at
/home/marxin/Programming/gcc/gcc/tree-cfg.c:2261
#10 0x000000000097a58a in delete_basic_block (bb=bb@entry=<basic_block
0x7ffff6b5b888 (7)>) at /home/marxin/Programming/gcc/gcc/cfghooks.c:599
#11 0x0000000000e0a179 in cleanup_control_flow_pre () at
/home/marxin/Programming/gcc/gcc/tree-cfgcleanup.c:785
#12 0x0000000000e0a5ba in cleanup_tree_cfg_noloop () at
/home/marxin/Programming/gcc/gcc/tree-cfgcleanup.c:881
#13 cleanup_tree_cfg () at
/home/marxin/Programming/gcc/gcc/tree-cfgcleanup.c:989
#14 0x0000000000ce5c0d in execute_function_todo (fn=0x7ffff6d21160,
data=<optimized out>) at /home/marxin/Programming/gcc/gcc/passes.c:1930
#15 0x0000000000ce6aaf in execute_todo (flags=96) at
/home/marxin/Programming/gcc/gcc/passes.c:2031
#16 0x0000000000ce8cc7 in execute_one_pass (pass=<opt_pass* 0x22c8700
"fre"(38)>) at /home/marxin/Programming/gcc/gcc/passes.c:2520
#17 0x0000000000ce9198 in execute_pass_list_1 (pass=<opt_pass* 0x22c8700
"fre"(38)>) at /home/marxin/Programming/gcc/gcc/passes.c:2569
#18 0x0000000000ce91aa in execute_pass_list_1 (pass=<opt_pass* 0x22c83e0
"early_optimizations"(31)>) at /home/marxin/Programming/gcc/gcc/passes.c:2570
#19 0x0000000000ce91e9 in execute_pass_list (fn=0x7ffff6d21160, pass=<optimized
out>) at /home/marxin/Programming/gcc/gcc/passes.c:2580
#20 0x0000000000cf1438 in do_per_function_toporder (callback=0xce91d0
<execute_pass_list(function*, opt_pass*)>, data=0x22c8260) at
/home/marxin/Programming/gcc/gcc/passes.c:1705
#21 0x0000000000cf1473 in execute_ipa_pass_list (pass=<opt_pass* 0x22c8200
"opt_local_passes"(27)>) at /home/marxin/Programming/gcc/gcc/passes.c:2928
#22 0x00000000009ae9a3 in ipa_passes () at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2482
#23 symbol_table::compile (this=0x7ffff6b56100) at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2618
#24 0x00000000009b0d3d in symbol_table::compile (this=0x7ffff6b56100) at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2863
#25 symbol_table::finalize_compilation_unit (this=0x7ffff6b56100) at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2863
#26 0x0000000000dbca8b in compile_file () at
/home/marxin/Programming/gcc/gcc/toplev.c:481
#27 0x00000000007a8e1a in do_compile () at
/home/marxin/Programming/gcc/gcc/toplev.c:2176
#28 toplev::main (this=this@entry=0x7fffffffdabe, argc=<optimized out>,
argc@entry=15, argv=<optimized out>, argv@entry=0x7fffffffdbb8) at
/home/marxin/Programming/gcc/gcc/toplev.c:2311
#29 0x00000000007ac46b in main (argc=15, argv=0x7fffffffdbb8) at
/home/marxin/Programming/gcc/gcc/main.c:39
>From gcc-bugs-return-629988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:23:06 2019
Return-Path: <gcc-bugs-return-629988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99137 invoked by alias); 21 Jan 2019 12:23:05 -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 99051 invoked by uid 48); 21 Jan 2019 12:23:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88945] ICE in fold_convert_loc in FRE when using -fdump-tree-fre-details
Date: Mon, 21 Jan 2019 12:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone cf_known_to_fail
Message-ID: <bug-88945-4-39U0E3Zy5P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88945-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: 2019-01/txt/msg02797.txt.bz2
Content-length: 542

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |9.0
      Known to fail|                            |8.2.0, 9.0

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Note that original test-case is ./libgomp/testsuite/libgomp.fortran/task2.f90
(with commented out 'use omp_lib').
>From gcc-bugs-return-629989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:25:09 2019
Return-Path: <gcc-bugs-return-629989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102249 invoked by alias); 21 Jan 2019 12:25:09 -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 102101 invoked by uid 55); 21 Jan 2019 12:25:03 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/71659] _xgetbv intrinsic missing
Date: Mon, 21 Jan 2019 12:25: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-71659-4-cNWsffYSZ3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71659-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: 2019-01/txt/msg02798.txt.bz2
Content-length: 2233

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

--- Comment #6 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Mon Jan 21 12:23:49 2019
New Revision: 268113

URL: https://gcc.gnu.org/viewcvs?rev=268113&root=gcc&view=rev
Log:
i386: Move Intel intrinsics head files to <immintrin.h>

According to Intel Intrinsics Guide:

https://software.intel.com/sites/landingpage/IntrinsicsGuide/

Intel intrinsics should be available by including <immintrin.h>.  This
patch moves remaining Intel intrinsics head files from <x86intrin.h> to
<immintrin.h>.

        PR target/71659
        * config/i386/adxintrin.h: Just check _IMMINTRIN_H_INCLUDED.
        * config/i386/clflushoptintrin.h: Check _IMMINTRIN_H_INCLUDED
        instead of _X86INTRIN_H_INCLUDED.
        * onfig/i386/clwbintrin.h: Likewise.
        * config/i386/pkuintrin.h: Likewise.
        * config/i386/prfchwintrin.h: Likewise.
        * config/i386/rdseedintrin.h: Likewise.
        * config/i386/wbnoinvdintrin.h: Likewise.
        * config/i386/xsavecintrin.h: Likewise.
        * config/i386/xsavesintrin.h: Likewise.
        * config/i386/fxsrintrin.h: Enable _IMMINTRIN_H_INCLUDED check.
        * config/i386/xsaveintrin.h: Likewise.
        * config/i386/xsaveoptintrin.h: Likewise.
        * config/i386/x86intrin.h: Move "#include" <rdseedintrin.h>,
        <prfchwintrin.h>, <fxsrintrin.h>, <xsaveintrin.h>,
        <xsaveoptintrin.h>, <adxintrin.h>, <clwbintrin.h>,
        <clflushoptintrin.h>, <xsavesintrin.h>, <xsavecintrin.h>,
        <wbnoinvdintrin.h> and <pkuintrin.h> to ...
        * config/i386/immintrin.h: Here.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/adxintrin.h
    trunk/gcc/config/i386/clflushoptintrin.h
    trunk/gcc/config/i386/clwbintrin.h
    trunk/gcc/config/i386/fxsrintrin.h
    trunk/gcc/config/i386/immintrin.h
    trunk/gcc/config/i386/pkuintrin.h
    trunk/gcc/config/i386/prfchwintrin.h
    trunk/gcc/config/i386/rdseedintrin.h
    trunk/gcc/config/i386/wbnoinvdintrin.h
    trunk/gcc/config/i386/x86intrin.h
    trunk/gcc/config/i386/xsavecintrin.h
    trunk/gcc/config/i386/xsaveintrin.h
    trunk/gcc/config/i386/xsaveoptintrin.h
    trunk/gcc/config/i386/xsavesintrin.h
>From gcc-bugs-return-629990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:27:20 2019
Return-Path: <gcc-bugs-return-629990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107246 invoked by alias); 21 Jan 2019 12:27: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 107123 invoked by uid 48); 21 Jan 2019 12:27:15 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 12:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-FtRWgyfiVu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02799.txt.bz2
Content-length: 560

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

--- Comment #11 from Wilco <wilco at gcc dot gnu.org> ---
A SPEC2006 run shows the codesize cost of make_more_copies is 0.05%.
Practically all tests are worse, the largest increases are perlbench at 0.20%,
gromacs 0.12%, calculix 0.12%, soplex 0.08%, xalancbmk 0.07%, wrf 0.06%. In
total ~26KBytes of extra moves...

Overall this doesn't look like a good change. So the question is, what is the
purpose of adding extra live ranges when the register allocator doesn't appear
to be able to merge them?
>From gcc-bugs-return-629991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:29:11 2019
Return-Path: <gcc-bugs-return-629991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110695 invoked by alias); 21 Jan 2019 12:29:11 -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 110578 invoked by uid 48); 21 Jan 2019 12:29:07 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/71659] _xgetbv intrinsic missing
Date: Mon, 21 Jan 2019 12:29: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-71659-4-SLYNNpcune@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71659-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: 2019-01/txt/msg02800.txt.bz2
Content-length: 928

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |9.0

--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Daniel Fruzynski from comment #4)
> This intrinsics was added in gcc 8. Initial implementation was buggy (see
> r85684) and was fixed in 8.2 However there is one more issue here: Intel
> Intrinsics Guide says that it should be available by including
> <immintrin.h>, however in gcc you need to include <xsaveintrin.h>.

Fixed for GCC 9.

> Additionally there are no defines for XFEATURE_ENABLED_MASK and possible
> output values.

I will investigate it.
>From gcc-bugs-return-629993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:29:39 2019
Return-Path: <gcc-bugs-return-629993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112435 invoked by alias); 21 Jan 2019 12:29: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 112187 invoked by uid 48); 21 Jan 2019 12:29:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86590] Codegen is poor when passing std::string by value with _GLIBCXX_EXTERN_TEMPLATE undefined
Date: Mon, 21 Jan 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86590-4-qRJ7GqURer@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86590-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86590-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: 2019-01/txt/msg02802.txt.bz2
Content-length: 833

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

--- Comment #33 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> As Marc said, the only difference is the explicit instantiation
> declarations. You'll get the same in C++14 if you disable them:
> 
> #include <bits/c++config.h>
> #undef _GLIBCXX_EXTERN_TEMPLATE
> #include <string>
> // ...
> 
> They're only disabled temporarily for C++17 until our C++17 support is
> stable, at which point we'll start exporting the new C++17 members of
> std::string from libstdc++.so and re-enable the explicit instantiation
> declarations.

N.B. this has happened on trunk for C++17 mode. To test the current state you
need to disable the explicit instantiations, either by compiling with
-std=gnu++2a or via the #undef shown above.
>From gcc-bugs-return-629992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:29:12 2019
Return-Path: <gcc-bugs-return-629992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110838 invoked by alias); 21 Jan 2019 12:29:12 -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 110621 invoked by uid 48); 21 Jan 2019 12:29:08 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88918] [meta-bug] x86 intrinsic issues
Date: Mon, 21 Jan 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
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: bug_status resolution
Message-ID: <bug-88918-4-ziMe9hGKcT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88918-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88918-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: 2019-01/txt/msg02801.txt.bz2
Content-length: 451

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88918
Bug 88918 depends on bug 71659, which changed state.

Bug 71659 Summary: _xgetbv intrinsic missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71659

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
>From gcc-bugs-return-629995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:31:08 2019
Return-Path: <gcc-bugs-return-629995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114700 invoked by alias); 21 Jan 2019 12:31:07 -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 114600 invoked by uid 48); 21 Jan 2019 12:31:03 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Mon, 21 Jan 2019 12:31: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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:
Message-ID: <bug-88906-4-5kcDIHMzhv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg02804.txt.bz2
Content-length: 184

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

--- Comment #7 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
*** Bug 86334 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-629994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:31:07 2019
Return-Path: <gcc-bugs-return-629994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114686 invoked by alias); 21 Jan 2019 12:31:07 -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 114558 invoked by uid 48); 21 Jan 2019 12:31:02 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86334] wrong code with -march=athlon -mmemcpy-strategy=libcall:-1:noalign
Date: Mon, 21 Jan 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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_status resolution
Message-ID: <bug-86334-4-FDFwyPSTFG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86334-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86334-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: 2019-01/txt/msg02803.txt.bz2
Content-length: 504

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #3 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Dup of PR88906.

*** This bug has been marked as a duplicate of bug 88906 ***
>From gcc-bugs-return-629996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:33:40 2019
Return-Path: <gcc-bugs-return-629996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126605 invoked by alias); 21 Jan 2019 12:33:40 -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 124122 invoked by uid 48); 21 Jan 2019 12:33:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88935] std::random_shuffle does not work if the sequence is longer than RAND_MAX elements
Date: Mon, 21 Jan 2019 12:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88935-4-7n1SI3T2If@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88935-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: 2019-01/txt/msg02805.txt.bz2
Content-length: 402

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1
>From gcc-bugs-return-629997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:37:46 2019
Return-Path: <gcc-bugs-return-629997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15280 invoked by alias); 21 Jan 2019 12:37: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 15209 invoked by uid 48); 21 Jan 2019 12:37:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Mon, 21 Jan 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-jd09SNgyxb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg02806.txt.bz2
Content-length: 262

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

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Started with r257233, where a new memcpy call builtin is introduced.
Arseny, are you sure it fails also for GCC 6.* and GCC 7.* branches?
>From gcc-bugs-return-629998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:42:31 2019
Return-Path: <gcc-bugs-return-629998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34308 invoked by alias); 21 Jan 2019 12:42:30 -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 34218 invoked by uid 48); 21 Jan 2019 12:42:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88945] ICE in fold_convert_loc in FRE when using -fdump-tree-fre-details
Date: Mon, 21 Jan 2019 12:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88945-4-9U6SyTJN3h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88945-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: 2019-01/txt/msg02807.txt.bz2
Content-length: 558

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

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
One more example that started to ICE with r247882:

$ gcc /home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/char_result_13.f90
-c -O -fdump-tree-fre-details
during GIMPLE pass: fre
dump file: char_result_13.f90.037t.fre1
gcc: internal compiler error: Segmentation fault signal terminated program f951
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.
>From gcc-bugs-return-629999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:42:33 2019
Return-Path: <gcc-bugs-return-629999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34580 invoked by alias); 21 Jan 2019 12:42:32 -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 34249 invoked by uid 48); 21 Jan 2019 12:42:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88905] [8/9 Regression] ICE: in decompose, at rtl.h:2253 with -mabm and __builtin_popcountll
Date: Mon, 21 Jan 2019 12:42: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88905-4-9nuwtA3AgK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88905-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: 2019-01/txt/msg02808.txt.bz2
Content-length: 678

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |jakub at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe the only change that revision does is set gimple_location somewhere
and that makes TER do a different decision.
In any case, this is expansion bug.
>From gcc-bugs-return-630000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:43:45 2019
Return-Path: <gcc-bugs-return-630000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36784 invoked by alias); 21 Jan 2019 12:43:45 -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 36756 invoked by uid 89); 21 Jan 2019 12:43:44 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=2.1 required=5.0 testsºYES_50,HTML_MESSAGE,RCVD_IN_RP_RNBL,SPF_FAIL autolearn=no version=3.3.2 spammy=CLICK, userid, upgrade, zimbra
X-HELO: mail.comercioexterior.gob.ec
Received: from mail.comercioexterior.gob.ec (HELO mail.comercioexterior.gob.ec) (190.152.45.35) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 21 Jan 2019 12:43:42 +0000
Received: from localhost (localhost [127.0.0.1])	by mail.comercioexterior.gob.ec (Postfix) with ESMTP id A51C63A67367	for <gcc-bugs@gcc.gnu.org>; Mon, 21 Jan 2019 07:31:24 -0500 (-05)
Received: from mail.comercioexterior.gob.ec ([127.0.0.1])	by localhost (mail.comercioexterior.gob.ec [127.0.0.1]) (amavisd-new, port 10032)	with ESMTP id MafplqrP96_T for <gcc-bugs@gcc.gnu.org>;	Mon, 21 Jan 2019 07:31:17 -0500 (-05)
Received: from localhost (localhost [127.0.0.1])	by mail.comercioexterior.gob.ec (Postfix) with ESMTP id 6FB3E3A6B7A8	for <gcc-bugs@gcc.gnu.org>; Mon, 21 Jan 2019 06:11:55 -0500 (-05)
Received: from mail.comercioexterior.gob.ec ([127.0.0.1])	by localhost (mail.comercioexterior.gob.ec [127.0.0.1]) (amavisd-new, port 10026)	with ESMTP id GqMskZu_q3gx for <gcc-bugs@gcc.gnu.org>;	Mon, 21 Jan 2019 06:11:55 -0500 (-05)
Received: from rdpp.lbjfsv11b25ubdk2obws1ui2hc.qx.internal.cloudapp.net (unknown [192.168.21.99])	by mail.comercioexterior.gob.ec (Postfix) with ESMTPSA id 06DB63A69778	for <gcc-bugs@gcc.gnu.org>; Mon, 21 Jan 2019 05:14:44 -0500 (-05)
MIME-Version: 1.0
Subject: email update for gcc-bugs@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "Zimbra Help Desk via gcc-bugs" <gcc-bugs@gcc.gnu.org>
Reply-To: "Zimbra Help Desk" <helpdesks.zimbras@zimbra.com>
Date: Mon, 21 Jan 2019 12:43:00 -0000
Message-Id: <20190121101446.06DB63A69778@mail.comercioexterior.gob.ec>
Content-Description: Mail message body
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2019-01/txt/msg02809.txt.bz2
Content-length: 305

This is to inform you that we will be undergoing system upgrade/maintenance of our systems between 10pm-11pm today.As a result you will be required to verify your email by CLICK HERE in order for us to upgrade your Zimbra account. Once again we are sorry for any inconveniences this might cause you
>From gcc-bugs-return-630001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:44:51 2019
Return-Path: <gcc-bugs-return-630001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38301 invoked by alias); 21 Jan 2019 12:44:51 -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 38206 invoked by uid 48); 21 Jan 2019 12:44:47 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/86590] Codegen is poor when passing std::string by value with _GLIBCXX_EXTERN_TEMPLATE undefined
Date: Mon, 21 Jan 2019 12:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-86590-4-7gIRzFZeYm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86590-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86590-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: 2019-01/txt/msg02810.txt.bz2
Content-length: 425

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

Marc Glisse <glisse at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libstdc++                   |ipa

--- Comment #34 from Marc Glisse <glisse at gcc dot gnu.org> ---
Recategorizing, the libstdc++ part seems fixed, the rest is inlining.
>From gcc-bugs-return-630003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:46:34 2019
Return-Path: <gcc-bugs-return-630003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41704 invoked by alias); 21 Jan 2019 12:46:34 -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 41582 invoked by uid 48); 21 Jan 2019 12:46:30 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/87615] Possible excessive compile time with -O2
Date: Mon, 21 Jan 2019 12:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm 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: bug_status assigned_to
Message-ID: <bug-87615-4-rLsaqVkgH2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87615-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: 2019-01/txt/msg02812.txt.bz2
Content-length: 556

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

Martin Jambor <jamborm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
           Assignee|jamborm at gcc dot gnu.org         |unassigned at gcc dot gnu.org

--- Comment #14 from Martin Jambor <jamborm at gcc dot gnu.org> ---
For now at least I'm done with this PR, I'm not sure how easy it is to improve
the compile time further.
>From gcc-bugs-return-630002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:46:07 2019
Return-Path: <gcc-bugs-return-630002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40099 invoked by alias); 21 Jan 2019 12:46:07 -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 39745 invoked by uid 48); 21 Jan 2019 12:45:51 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 12:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-5Hro4CzV3I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02811.txt.bz2
Content-length: 469

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

--- Comment #12 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Before the change combine forwarded all argument (etc.) hard registers wherever
it could, doing part of RA's job (and doing a lousy job of it).  If after the
change it no longer two ranges, than a) that is a good decision, or b) there is
some bug in RA.

0.05% code size is nothing, most other biggish changes have a much bigger
effect.
>From gcc-bugs-return-630005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:54:09 2019
Return-Path: <gcc-bugs-return-630005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74387 invoked by alias); 21 Jan 2019 12:54:09 -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 74243 invoked by uid 48); 21 Jan 2019 12:54:04 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88918] [meta-bug] x86 intrinsic issues
Date: Mon, 21 Jan 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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: bug_status resolution
Message-ID: <bug-88918-4-C1Dgz6QHPA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88918-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88918-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: 2019-01/txt/msg02814.txt.bz2
Content-length: 467

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88918
Bug 88918 depends on bug 49300, which changed state.

Bug 49300 Summary: [x86] Missing SSE4.1 intrinsic function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49300

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID
>From gcc-bugs-return-630004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:54:09 2019
Return-Path: <gcc-bugs-return-630004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74372 invoked by alias); 21 Jan 2019 12:54:09 -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 74220 invoked by uid 48); 21 Jan 2019 12:54:03 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49300] [x86] Missing SSE4.1 intrinsic function
Date: Mon, 21 Jan 2019 12:54: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: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail 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: bug_status resolution
Message-ID: <bug-49300-4-i4eYqg8vYn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49300-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49300-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: 2019-01/txt/msg02813.txt.bz2
Content-length: 900

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to Piotr Wyderski from comment #0)
> The _mm_extract_epi64() function is available only on x64, but
> according to the instruction set, its underlying pextrq instruction 
> has the following parameters:
> 
> PEXTRQ r/m64, xmm2, imm8
> 
> so the m64 mode is available also on 32-bit x86.

Not really.

$ more pextrq.s
        pextrq $1, %xmm0, a

$ gcc -c -m32 pextrq.s
pextrq.s: Assembler messages:
pextrq.s:1: Error: `pextrq' is only supported in 64-bit mode
>From gcc-bugs-return-630006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:59:36 2019
Return-Path: <gcc-bugs-return-630006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89487 invoked by alias); 21 Jan 2019 12:59:35 -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 89349 invoked by uid 48); 21 Jan 2019 12:59:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88945] ICE in fold_convert_loc in FRE when using -fdump-tree-fre-details
Date: Mon, 21 Jan 2019 12:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-88945-4-WIyz8qh4ZY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88945-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: 2019-01/txt/msg02815.txt.bz2
Content-length: 1358

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
   Target Milestone|9.0                         |---
     Ever confirmed|0                           |1

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  remove_bb dumping BB contents is fishy ... but the real culprit is
dump_generic_node doing

      op0 = array_ref_low_bound (node);
      op1 = array_ref_element_size (node);

      if (!integer_zerop (op0)
          || TREE_OPERAND (node, 2)
          || TREE_OPERAND (node, 3))
        {
          pp_string (pp, "{lb: ");
          dump_generic_node (pp, op0, spc, flags, false);
          pp_string (pp, " sz: ");
          dump_generic_node (pp, op1, spc, flags, false);
          pp_right_brace (pp);
        }
      break;

here operand 3 is a released SSA name.  fold_convert_loc deals with
ERROR_MARK TREE_TYPE but not NULL (as it is for SSA names).

I agree it's annoying but not sure to what extent we want to fix this...
(eventually using error_mark_node for released SSA names is an acceptable fix)
>From gcc-bugs-return-630007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 12:59:58 2019
Return-Path: <gcc-bugs-return-630007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91896 invoked by alias); 21 Jan 2019 12:59:58 -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 91775 invoked by uid 48); 21 Jan 2019 12:59:53 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80517] [missed optimization] constant propagation through Intel intrinsics
Date: Mon, 21 Jan 2019 12:59: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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:
Message-ID: <bug-80517-4-6tco9sesyA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80517-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: 2019-01/txt/msg02816.txt.bz2
Content-length: 140

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

--- Comment #7 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
See also PR55894.
>From gcc-bugs-return-630008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:01:32 2019
Return-Path: <gcc-bugs-return-630008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95591 invoked by alias); 21 Jan 2019 13:01:24 -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 93587 invoked by uid 48); 21 Jan 2019 13:00:45 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88946] New: [nvptx, openacc, libgomp] cuMemAlloc error for two empty asynchronous parallels
Date: Mon, 21 Jan 2019 13:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88946-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: 2019-01/txt/msg02817.txt.bz2
Content-length: 1779

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

            Bug ID: 88946
           Summary: [nvptx, openacc, libgomp] cuMemAlloc error for two
                    empty asynchronous parallels
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider test-case:
...
/* { dg-do run } */

int
main (void)
{
#pragma acc parallel async
  ;

#pragma acc parallel async
  ;

#pragma acc wait

  return 0;
}
...

This fails in execution:
...
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/test.c \
  -DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0  -O0  execution test
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/test.c \
  -DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0  -O2  execution test
...

with:
...
libgomp: cuMemAlloc error: invalid argument
Segmentation fault (core dumped)
...

because we're trying to allocate zero bytes:
...
Thread 1 "test.exe" hit Breakpoint 1, GOMP_PLUGIN_error (
    msg=msg@entry=0x7ffff6ea9987 "cuMemAlloc error: %s")
    at libgomp/libgomp-plugin.c:64
64      {
(gdb) up
#1  0x00007ffff6ea647c in cuda_map_create (size=0)
    at /home/vries/oacc/trunk/source-gcc/libgomp/plugin/plugin-nvptx.c:231
231       CUDA_CALL_ERET (NULL, cuMemAlloc, &map->d, size);
...

This causes cuda_map_create to return NULL, after which map in map_push map is
NULL, so we segfault at:
...
  s->map = map;
  s->map->active = true;
...

If we remove the async clauses from the test-case, it passes.  Still we call
map_push with size == 0, but that doesn't result in a cuda_map_create with size
== 0.
>From gcc-bugs-return-630009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:04:54 2019
Return-Path: <gcc-bugs-return-630009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122625 invoked by alias); 21 Jan 2019 13:04:54 -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 120635 invoked by uid 48); 21 Jan 2019 13:04:48 -0000
From: "tom at kera dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] New: regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Mon, 21 Jan 2019 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tom at kera dot name
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88947-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: 2019-01/txt/msg02818.txt.bz2
Content-length: 3466

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

            Bug ID: 88947
           Summary: regex_match doesn't fail early when given a
                    non-matching pattern with a start-of-input anchor
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tom at kera dot name
  Target Milestone: ---

I first raised this on SO (https://stackoverflow.com/q/54237547/560648), on
which I have posted some benchmarks to back up the claim(s) below.

Take the following:

#include <regex>
int main()
{
  static const size_t BufSize = 100;
  char buf[BufSize] = {};
  auto begin = std::cbegin(buf), end = std::cend(buf);

  std::cmatch groups;
  std::regex::flag_type flags = std::regex_constants::ECMAScript;
  std::regex re("^what", flags);
  std::regex_search(begin, end, groups, re);
}

This attempts to match the pattern "^what" against a block of 100 characters.
The match is not expected to succeed (in this case, the input is simply 100
'\0's, but the problem exists for any non-matching input).

However, I expect the match to fail as soon as the first character of input is
examined. By adjusting BufSize to increasingly large values, we observe that
the execution time increases also, suggesting that the regex engine is
examining the entire input even though the presence of the anchor "^"
guarantees that a match will never be found. It only needed to examine the
first character to know this. When BufSize reaches larger values like 100KB,
this becomes quite problematic.

It is clear from the implementation code
(https://github.com/gcc-mirror/gcc/blob/464ac146f6d2aaab847f653edde3ae84a8366c94/libstdc%2B%2B-v3/include/bits/regex_executor.tcc#L37-L54)
that there is simply no logic in place to "fail fast" or "fail early" in a case
like this: the only way a "no match" result is returned is after examining the
whole input, regardless of the pattern.

It is my opinion that this is a quality of implementation issue, and one that
only appears in C++ implementations of regular expressions. This problem is
common to libstdc++, libc++ and also Visual Studio's stdlib impl. (I am raising
bugs against all three.)

As a workaround I'm having to artificially select a prefix of the input data in
order to get a fast result -- in the example above, that could be:

  auto begin = std::cbegin(buf), end = std::cbegin(buf)+4;

However, not all examples are so trivial (indeed, the example above would be
much better approached with a simple string prefix comparison) and the
workaround not always so easy. When the pattern is more complex, it is not
always easy to find the best number of characters to send to the regex engine,
and the resulting code not particularly elegant. It would be much better if the
engine could be given the whole input without having to worry about scale.

Hopefully my expectation isn't unreasonable; Safari's implementation of regex
behaves as I'd expect. That is, the time to return a "no match" result is
constant (and fast) given the JS equivalent of the above example.

Is it possible that the regex_match implementation could be given a little more
intelligence?

(Apologies that I am not sufficiently familiar with libstdc++ version history
to select an appropriate version number for this bug.)
>From gcc-bugs-return-630010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:05:22 2019
Return-Path: <gcc-bugs-return-630010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7584 invoked by alias); 21 Jan 2019 13:05:22 -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 4653 invoked by uid 48); 21 Jan 2019 13:05:17 -0000
From: "florian.schornbaum at siemens dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88531] Index data types when targeting AVX-512 vectorization with gather/scatter
Date: Mon, 21 Jan 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: florian.schornbaum at siemens dot com
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:
Message-ID: <bug-88531-4-oRcqRal7wj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88531-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: 2019-01/txt/msg02819.txt.bz2
Content-length: 399

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

--- Comment #4 from Florian Schornbaum <florian.schornbaum at siemens dot com> ---
Hi Jakub, Richard,

I hope you both had a good start into 2019.

I'm still wondering if there are any plans to make arbitrary index data types
work with gather/scatter?

If there are no such plans at the moment, we will work around this issue on our
side.
>From gcc-bugs-return-630011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:07:04 2019
Return-Path: <gcc-bugs-return-630011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71815 invoked by alias); 21 Jan 2019 13:07: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 66558 invoked by uid 48); 21 Jan 2019 13:06:59 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Mon, 21 Jan 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88947-4-FGn8ifUtUY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg02820.txt.bz2
Content-length: 458

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Tomalak Geret'kal from comment #0)
> (Apologies that I am not sufficiently familiar with libstdc++ version
> history to select an appropriate version number for this bug.)

Libstdc++ doesn't have version numbers and you don't need to know history.
You're supposed to say what version of GCC you're reporting the bug against.
>From gcc-bugs-return-630012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:08:54 2019
Return-Path: <gcc-bugs-return-630012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74307 invoked by alias); 21 Jan 2019 13:08:54 -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 69845 invoked by uid 48); 21 Jan 2019 13:08:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Mon, 21 Jan 2019 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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: keywords bug_status cf_reconfirmed_on cc version everconfirmed bug_severity
Message-ID: <bug-88947-4-EKvCwWJzXa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg02821.txt.bz2
Content-length: 792

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
                 CC|                            |timshen at gcc dot gnu.org
            Version|unknown                     |8.2.0
     Ever confirmed|0                           |1
           Severity|normal                      |enhancement

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Confirmed for the latest release (and also present on trunk).
>From gcc-bugs-return-630013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:15:41 2019
Return-Path: <gcc-bugs-return-630013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39216 invoked by alias); 21 Jan 2019 13:15: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 38795 invoked by uid 48); 21 Jan 2019 13:15:05 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Mon, 21 Jan 2019 13:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-4i8EOV67PI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg02822.txt.bz2
Content-length: 243

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

--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
It does w/ -fchecking, but in a different way, so maybe these are really
unrelated issues: https://gcc.godbolt.org/z/BbN9DX
>From gcc-bugs-return-630016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:17:17 2019
Return-Path: <gcc-bugs-return-630016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45404 invoked by alias); 21 Jan 2019 13:17:17 -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 44046 invoked by uid 55); 21 Jan 2019 13:17:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87514] std::make_shared could avoid virtual call to _Sp_counted_ptr_inplace::_M_get_deleter()
Date: Mon, 21 Jan 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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:
Message-ID: <bug-87514-4-jDXUnntxA7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87514-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87514-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: 2019-01/txt/msg02825.txt.bz2
Content-length: 3716

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jan 21 13:16:25 2019
New Revision: 268114

URL: https://gcc.gnu.org/viewcvs?rev=268114&root=gcc&view=rev
Log:
PR libstdc++/88782 avoid ODR problems in std::make_shared

The old version of _Sp_counted_ptr_inplace::_M_get_deleter (up to GCC
8.2.0) expects to be passed a real std::typeinfo object, so mixing that
with the new definition of the __shared_ptr constructor (which always
passes the fake tag) leads to accessing the fake object as a real
std::typeinfo. Instead of trying to make it safe to mix the old and new
definitions, just stop using that function. By passing a reference to
__shared_ptr::_M_ptr to the __shared_count constructor it can be set
directly, without needing to obtain the pointer via the _M_get_deleter
back-channel. This avoids a virtual dispatch (which fixes PR 87514).

This means that code built against new libstdc++ headers doesn't use
_M_get_deleter at all, and so make_shared works the same whether RTTI is
enabled or not.

Unlike on trunk, where _M_get_deleter calls a new library function that
can detect the real type_info object even when RTTI is disabled, this
commit for gcc-8-branch cannot add a new symbol to the shared library.
That means _M_get_deleter still returns null if compiled without RTTI
and it gets called from a translation unit that was compiled with RTTI.

If linking to objects built against older versions of libstdc++ then if
all objects use -frtti or all use -fno-rtti, then the caller of
_M_get_deleter and the definition of _M_get_deleter will be consistent
and it will work. If mixing -frtti with -fno-rtti it can still fail if
the linker picks an old definition of _M_get_deleter and an old
__shared_ptr constructor that are incompatible. In that case some or all
objects might need to be recompiled (or just relinked in a different
order).

Backport from mainline
2019-01-18  Jonathan Wakely  <jwakely@redhat.com>

        PR libstdc++/87514
        PR libstdc++/87520
        PR libstdc++/88782
        * config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export new symbol.
        * include/bits/shared_ptr.h
        (shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...))
        (allocate_shared): Change to use new tag type.
        * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_eq):
        Declare new member function.
        (_Sp_alloc_shared_tag): Define new type.
        (_Sp_counted_ptr_inplace): Declare __shared_count<_Lp> as a friend.
        (_Sp_counted_ptr_inplace::_M_get_deleter) [!__cpp_rtti]: Use
        _Sp_make_shared_tag::_S_eq to check type_info.
        (__shared_count(Ptr, Deleter),__shared_count(Ptr, Deleter, Alloc)):
        Constrain to prevent being called with _Sp_alloc_shared_tag.
        (__shared_count(_Sp_make_shared_tag, const _Alloc&, Args&&...)):
        Replace constructor with ...
        (__shared_count(Tp*&, _Sp_alloc_shared_tag<_Alloc>, Args&&...)): Use
        reference parameter so address of the new object can be returned to
        the caller. Obtain the allocator from the tag type.
        (__shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...)): Replace
        constructor with ...
        (__shared_ptr(_Sp_alloc_shared_tag<Alloc>, Args&&...)): Pass _M_ptr
        to the __shared_count constructor.
        (__allocate_shared): Change to use new tag type.
        * src/c++11/shared_ptr.cc (_Sp_make_shared_tag::_S_eq): Define.

Modified:
    branches/gcc-8-branch/libstdc++-v3/ChangeLog
    branches/gcc-8-branch/libstdc++-v3/include/bits/shared_ptr.h
    branches/gcc-8-branch/libstdc++-v3/include/bits/shared_ptr_base.h
>From gcc-bugs-return-630015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:17:13 2019
Return-Path: <gcc-bugs-return-630015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44917 invoked by alias); 21 Jan 2019 13:17:12 -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 44130 invoked by uid 55); 21 Jan 2019 13:17:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87520] [8 Regression] ODR violations in std::make_shared when mixing -fno-rtti and -frtti
Date: Mon, 21 Jan 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87520-4-p9pJNtCGyR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87520-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87520-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: 2019-01/txt/msg02824.txt.bz2
Content-length: 3717

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

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jan 21 13:16:25 2019
New Revision: 268114

URL: https://gcc.gnu.org/viewcvs?rev=268114&root=gcc&view=rev
Log:
PR libstdc++/88782 avoid ODR problems in std::make_shared

The old version of _Sp_counted_ptr_inplace::_M_get_deleter (up to GCC
8.2.0) expects to be passed a real std::typeinfo object, so mixing that
with the new definition of the __shared_ptr constructor (which always
passes the fake tag) leads to accessing the fake object as a real
std::typeinfo. Instead of trying to make it safe to mix the old and new
definitions, just stop using that function. By passing a reference to
__shared_ptr::_M_ptr to the __shared_count constructor it can be set
directly, without needing to obtain the pointer via the _M_get_deleter
back-channel. This avoids a virtual dispatch (which fixes PR 87514).

This means that code built against new libstdc++ headers doesn't use
_M_get_deleter at all, and so make_shared works the same whether RTTI is
enabled or not.

Unlike on trunk, where _M_get_deleter calls a new library function that
can detect the real type_info object even when RTTI is disabled, this
commit for gcc-8-branch cannot add a new symbol to the shared library.
That means _M_get_deleter still returns null if compiled without RTTI
and it gets called from a translation unit that was compiled with RTTI.

If linking to objects built against older versions of libstdc++ then if
all objects use -frtti or all use -fno-rtti, then the caller of
_M_get_deleter and the definition of _M_get_deleter will be consistent
and it will work. If mixing -frtti with -fno-rtti it can still fail if
the linker picks an old definition of _M_get_deleter and an old
__shared_ptr constructor that are incompatible. In that case some or all
objects might need to be recompiled (or just relinked in a different
order).

Backport from mainline
2019-01-18  Jonathan Wakely  <jwakely@redhat.com>

        PR libstdc++/87514
        PR libstdc++/87520
        PR libstdc++/88782
        * config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export new symbol.
        * include/bits/shared_ptr.h
        (shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...))
        (allocate_shared): Change to use new tag type.
        * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_eq):
        Declare new member function.
        (_Sp_alloc_shared_tag): Define new type.
        (_Sp_counted_ptr_inplace): Declare __shared_count<_Lp> as a friend.
        (_Sp_counted_ptr_inplace::_M_get_deleter) [!__cpp_rtti]: Use
        _Sp_make_shared_tag::_S_eq to check type_info.
        (__shared_count(Ptr, Deleter),__shared_count(Ptr, Deleter, Alloc)):
        Constrain to prevent being called with _Sp_alloc_shared_tag.
        (__shared_count(_Sp_make_shared_tag, const _Alloc&, Args&&...)):
        Replace constructor with ...
        (__shared_count(Tp*&, _Sp_alloc_shared_tag<_Alloc>, Args&&...)): Use
        reference parameter so address of the new object can be returned to
        the caller. Obtain the allocator from the tag type.
        (__shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...)): Replace
        constructor with ...
        (__shared_ptr(_Sp_alloc_shared_tag<Alloc>, Args&&...)): Pass _M_ptr
        to the __shared_count constructor.
        (__allocate_shared): Change to use new tag type.
        * src/c++11/shared_ptr.cc (_Sp_make_shared_tag::_S_eq): Define.

Modified:
    branches/gcc-8-branch/libstdc++-v3/ChangeLog
    branches/gcc-8-branch/libstdc++-v3/include/bits/shared_ptr.h
    branches/gcc-8-branch/libstdc++-v3/include/bits/shared_ptr_base.h
>From gcc-bugs-return-630014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:17:12 2019
Return-Path: <gcc-bugs-return-630014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44833 invoked by alias); 21 Jan 2019 13:17:12 -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 43755 invoked by uid 55); 21 Jan 2019 13:17:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] [8/9 Regression] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc > 8.2
Date: Mon, 21 Jan 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88782-4-fJgVsjeqqY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-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: 2019-01/txt/msg02823.txt.bz2
Content-length: 3716

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jan 21 13:16:25 2019
New Revision: 268114

URL: https://gcc.gnu.org/viewcvs?rev=268114&root=gcc&view=rev
Log:
PR libstdc++/88782 avoid ODR problems in std::make_shared

The old version of _Sp_counted_ptr_inplace::_M_get_deleter (up to GCC
8.2.0) expects to be passed a real std::typeinfo object, so mixing that
with the new definition of the __shared_ptr constructor (which always
passes the fake tag) leads to accessing the fake object as a real
std::typeinfo. Instead of trying to make it safe to mix the old and new
definitions, just stop using that function. By passing a reference to
__shared_ptr::_M_ptr to the __shared_count constructor it can be set
directly, without needing to obtain the pointer via the _M_get_deleter
back-channel. This avoids a virtual dispatch (which fixes PR 87514).

This means that code built against new libstdc++ headers doesn't use
_M_get_deleter at all, and so make_shared works the same whether RTTI is
enabled or not.

Unlike on trunk, where _M_get_deleter calls a new library function that
can detect the real type_info object even when RTTI is disabled, this
commit for gcc-8-branch cannot add a new symbol to the shared library.
That means _M_get_deleter still returns null if compiled without RTTI
and it gets called from a translation unit that was compiled with RTTI.

If linking to objects built against older versions of libstdc++ then if
all objects use -frtti or all use -fno-rtti, then the caller of
_M_get_deleter and the definition of _M_get_deleter will be consistent
and it will work. If mixing -frtti with -fno-rtti it can still fail if
the linker picks an old definition of _M_get_deleter and an old
__shared_ptr constructor that are incompatible. In that case some or all
objects might need to be recompiled (or just relinked in a different
order).

Backport from mainline
2019-01-18  Jonathan Wakely  <jwakely@redhat.com>

        PR libstdc++/87514
        PR libstdc++/87520
        PR libstdc++/88782
        * config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export new symbol.
        * include/bits/shared_ptr.h
        (shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...))
        (allocate_shared): Change to use new tag type.
        * include/bits/shared_ptr_base.h (_Sp_make_shared_tag::_S_eq):
        Declare new member function.
        (_Sp_alloc_shared_tag): Define new type.
        (_Sp_counted_ptr_inplace): Declare __shared_count<_Lp> as a friend.
        (_Sp_counted_ptr_inplace::_M_get_deleter) [!__cpp_rtti]: Use
        _Sp_make_shared_tag::_S_eq to check type_info.
        (__shared_count(Ptr, Deleter),__shared_count(Ptr, Deleter, Alloc)):
        Constrain to prevent being called with _Sp_alloc_shared_tag.
        (__shared_count(_Sp_make_shared_tag, const _Alloc&, Args&&...)):
        Replace constructor with ...
        (__shared_count(Tp*&, _Sp_alloc_shared_tag<_Alloc>, Args&&...)): Use
        reference parameter so address of the new object can be returned to
        the caller. Obtain the allocator from the tag type.
        (__shared_ptr(_Sp_make_shared_tag, const Alloc&, Args&&...)): Replace
        constructor with ...
        (__shared_ptr(_Sp_alloc_shared_tag<Alloc>, Args&&...)): Pass _M_ptr
        to the __shared_count constructor.
        (__allocate_shared): Change to use new tag type.
        * src/c++11/shared_ptr.cc (_Sp_make_shared_tag::_S_eq): Define.

Modified:
    branches/gcc-8-branch/libstdc++-v3/ChangeLog
    branches/gcc-8-branch/libstdc++-v3/include/bits/shared_ptr.h
    branches/gcc-8-branch/libstdc++-v3/include/bits/shared_ptr_base.h
>From gcc-bugs-return-630017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:27:27 2019
Return-Path: <gcc-bugs-return-630017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121927 invoked by alias); 21 Jan 2019 13:27:27 -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 121804 invoked by uid 48); 21 Jan 2019 13:27:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88531] Index data types when targeting AVX-512 vectorization with gather/scatter
Date: Mon, 21 Jan 2019 13:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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:
Message-ID: <bug-88531-4-kh4NbJnRZ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88531-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: 2019-01/txt/msg02826.txt.bz2
Content-length: 344

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Certainly not in the immediate future, GCC 9 is now in stage4 and will remains
in regression bugfixing mode until usually mid April.  Even after that, I'll be
busy with OpenMP 5, but somebody else could implement it too.
>From gcc-bugs-return-630019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:29:48 2019
Return-Path: <gcc-bugs-return-630019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2450 invoked by alias); 21 Jan 2019 13:29:48 -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 2383 invoked by uid 48); 21 Jan 2019 13:29:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87520] [8 Regression] ODR violations in std::make_shared when mixing -fno-rtti and -frtti
Date: Mon, 21 Jan 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87520-4-9RFv2LWjL5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87520-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87520-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: 2019-01/txt/msg02828.txt.bz2
Content-length: 176

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

--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
A more reliable fix has been committed for 8.3 and 9.1
>From gcc-bugs-return-630018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:29:13 2019
Return-Path: <gcc-bugs-return-630018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128743 invoked by alias); 21 Jan 2019 13:29:12 -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 127006 invoked by uid 48); 21 Jan 2019 13:29:06 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87514] std::make_shared could avoid virtual call to _Sp_counted_ptr_inplace::_M_get_deleter()
Date: Mon, 21 Jan 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-87514-4-eoojtkeMiT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87514-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87514-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: 2019-01/txt/msg02827.txt.bz2
Content-length: 496

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |8.3

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Done for gcc 8.3 and 9.1
>From gcc-bugs-return-630020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:31:51 2019
Return-Path: <gcc-bugs-return-630020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7242 invoked by alias); 21 Jan 2019 13:31:51 -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 7105 invoked by uid 48); 21 Jan 2019 13:31:46 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] [8/9 Regression] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc > 8.2
Date: Mon, 21 Jan 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88782-4-raskBQYguA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-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: 2019-01/txt/msg02829.txt.bz2
Content-length: 541

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.3, thanks for the report that allowed this to be fixed before the
problem made it into any official release!
>From gcc-bugs-return-630021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:33:46 2019
Return-Path: <gcc-bugs-return-630021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9620 invoked by alias); 21 Jan 2019 13:33: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 9556 invoked by uid 48); 21 Jan 2019 13:33:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88905] [8/9 Regression] ICE: in decompose, at rtl.h:2253 with -mabm and __builtin_popcountll
Date: Mon, 21 Jan 2019 13:33: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88905-4-aUfZvrEliq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88905-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: 2019-01/txt/msg02830.txt.bz2
Content-length: 253

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45479
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45479&action=edit
gcc9-pr88905.patch

Untested fix.
>From gcc-bugs-return-630022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 13:57:03 2019
Return-Path: <gcc-bugs-return-630022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10577 invoked by alias); 21 Jan 2019 13:57:03 -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 10441 invoked by uid 48); 21 Jan 2019 13:56:59 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 13:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-HIUBjpfsfQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02831.txt.bz2
Content-length: 1081

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

--- Comment #13 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #12)
> Before the change combine forwarded all argument (etc.) hard registers
> wherever
> it could, doing part of RA's job (and doing a lousy job of it).  If after the
> change it no longer two ranges, than a) that is a good decision, or b) there
> is
> some bug in RA.

I think it's important not to conflate avoiding increasing live ranges of hard
registers and inserting redundant extra moves which cannot be optimized. The
former unconditionally looks like a good idea, however I can't see any valid
reasoning for the latter. Basically we now always get 2 moves for every
physical register, and this seems to thwart register preferencing.

> 0.05% code size is nothing, most other biggish changes have a much bigger
> effect.

Compiler optimization is all about making many small changes which add up to a
large improvement. This is actually quite significant given practically all
code is affected negatively.
>From gcc-bugs-return-630023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:07:46 2019
Return-Path: <gcc-bugs-return-630023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66190 invoked by alias); 21 Jan 2019 14:07: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 66062 invoked by uid 48); 21 Jan 2019 14:07:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88948] New: [9 Regression] ICE in elimination_costs_in_insn, at reload1.c:3640 since r264148
Date: Mon, 21 Jan 2019 14:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost
Message-ID: <bug-88948-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: 2019-01/txt/msg02832.txt.bz2
Content-length: 1711

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

            Bug ID: 88948
           Summary: [9 Regression] ICE in elimination_costs_in_insn, at
                    reload1.c:3640 since r264148
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: uros at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu

I see following ICE:

$ gcc
/home/marxin/Programming/gcc/gcc/testsuite/gcc.c-torture/execute/stdarg-3.c 
-fgcse-sm -O2 -msse3 -m32
during RTL pass: ira
/home/marxin/Programming/gcc/gcc/testsuite/gcc.c-torture/execute/stdarg-3.c: In
function â€˜f4â€™:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.c-torture/execute/stdarg-3.c:65:1:
internal compiler error: in elimination_costs_in_insn, at reload1.c:3640
   65 | }
      | ^
0xca6dd5 elimination_costs_in_insn
        /home/marxin/Programming/gcc/gcc/reload1.c:3637
0xca76cc calculate_elim_costs_all_insns()
        /home/marxin/Programming/gcc/gcc/reload1.c:1609
0xb5e85d ira_costs()
        /home/marxin/Programming/gcc/gcc/ira-costs.c:2298
0xb58069 ira_build()
        /home/marxin/Programming/gcc/gcc/ira-build.c:3432
0xb4eaaf ira
        /home/marxin/Programming/gcc/gcc/ira.c:5305
0xb4eaaf execute
        /home/marxin/Programming/gcc/gcc/ira.c:5616
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-630024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:08:00 2019
Return-Path: <gcc-bugs-return-630024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85968 invoked by alias); 21 Jan 2019 14:08:00 -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 77827 invoked by uid 48); 21 Jan 2019 14:07:57 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88948] [9 Regression] ICE in elimination_costs_in_insn, at reload1.c:3640 since r264148
Date: Mon, 21 Jan 2019 14:08: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88948-4-GUMMiLyQ6n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88948-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: 2019-01/txt/msg02833.txt.bz2
Content-length: 567

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
      Known to work|                            |8.2.0
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1
      Known to fail|                            |9.0
>From gcc-bugs-return-630025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:10:08 2019
Return-Path: <gcc-bugs-return-630025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109562 invoked by alias); 21 Jan 2019 14:10:07 -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 105709 invoked by uid 48); 21 Jan 2019 14:09:54 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88949] New: ICE in expand_expr_real_1, at expr.c:10001 with -fopenmp
Date: Mon, 21 Jan 2019 14:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88949-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: 2019-01/txt/msg02834.txt.bz2
Content-length: 1220

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

            Bug ID: 88949
           Summary: ICE in expand_expr_real_1, at expr.c:10001 with
                    -fopenmp
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: openmp
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org
  Target Milestone: ---

Probably quite old issue:

$ cat parallel_firstprivate_codegen.cpp
struct a {
  int b;
  a(int) {
#pragma omp parallel firstprivate(b)
    --b;
  }
};

int c;
int main() { a d(c); }

$ g++ parallel_firstprivate_codegen.cpp -fopenmp
during RTL pass: expand
parallel_firstprivate_codegen.cpp: In constructor â€˜a::a(int)â€™:
parallel_firstprivate_codegen.cpp:4:37: internal compiler error: in
expand_expr_real_1, at expr.c:10001
 #pragma omp parallel firstprivate(b)
                                     ^
0x7ffff6996fea __libc_start_main
        ../csu/libc-start.c:308


Reduced from:
https://github.com/llvm-mirror/clang/blob/master/test/OpenMP/parallel_firstprivate_codegen.cpp
>From gcc-bugs-return-630026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:34:23 2019
Return-Path: <gcc-bugs-return-630026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111163 invoked by alias); 21 Jan 2019 14:34:22 -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 110826 invoked by uid 48); 21 Jan 2019 14:34:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Mon, 21 Jan 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcchost cf_known_to_fail
Message-ID: <bug-88933-4-QUij264cSG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg02835.txt.bz2
Content-length: 511

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Host|                            |x86_64-pc-linux-gnu
      Known to fail|                            |4.8.0

--- Comment #4 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed that, it's as old as GCC 4.8.0. I can reproduce that on x86_64.
>From gcc-bugs-return-630027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:41:50 2019
Return-Path: <gcc-bugs-return-630027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4677 invoked by alias); 21 Jan 2019 14:41:49 -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 4552 invoked by uid 48); 21 Jan 2019 14:41:42 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Mon, 21 Jan 2019 14:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88933-4-ZgeyBtZD5f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg02836.txt.bz2
Content-length: 3624

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org,
                   |                            |mjambor at suse dot cz

--- Comment #5 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Reduced test-case for x86_64:

$ !$omp parallel  
!$omp single
  call a
!$omp end single
!$omp end parallel
contains
  subroutine b (c, d, e, f, g, h, i, j, k, m)
    character (*) c
    character  d
    integer, dimension (m) :: e
    integer, dimension (m) :: f
    character  g
    character  h
    real, dimension (:, :, :) :: i
    double precision, dimension (:, :, :) :: j
    integer, dimension (:, :, :) :: k

    integer, dimension (m) :: l
!$omp task firstprivate (k) firstprivate (l)
    !$omp end task
  c = ''
  end  
  subroutine a
    character  c
    character  d
    integer, dimension (7) :: e
    integer, dimension (7) :: f
    character g
    character h
    real, dimension (5, 6, 7) :: i
    double precision, dimension (6, 6, 7) :: j
    integer, dimension (5, 7, 6) :: k
    call b (c, d, e, f, g, h, i, j, k, 7)
  end  
end

$ ./xgcc -B. ~/Programming/testcases/god.f90 -c -std=legacy -O1 -fexceptions
-fipa-cp -fnon-call-exceptions -fopenmp -fno-inline-functions-called-once
b.2041.constprop.1/15 (b.constprop) @0x7ffff6c65e60
  Type: function definition analyzed
  Visibility: artificial
  References: 
  Referring: 
  Availability: local
  First run: 0
  Function flags: count: 1073741826 (estimated locally) body local
  Called by: a/0 (1073741825 (estimated locally),1.00 per call) (can throw
external) 
  Calls: __builtin_memset/12 (445388109 (estimated locally),0.41 per call)
__builtin_free/14 (0,0.00 per call) 
during IPA pass: inline
/home/marxin/Programming/testcases/god.f90:7:0: internal compiler error:
verify_cgraph_node failed
0xaa864f cgraph_node::verify_node()
        ../../gcc/cgraph.c:3555
0xa95d17 symtab_node::verify()
        ../../gcc/symtab.c:1204
0x1110c0f optimize_inline_calls(tree_node*)
        ../../gcc/tree-inline.c:5086
0x1a2e4ee inline_transform(cgraph_node*)
        ../../gcc/ipa-inline-transform.c:682
0xf2aba1 execute_one_ipa_transform_pass
        ../../gcc/passes.c:2239
0xf2ad2b execute_all_ipa_transforms()
        ../../gcc/passes.c:2281
0xab5abe cgraph_node::expand()
        ../../gcc/cgraphunit.c:2132
0xab612d expand_all_functions
        ../../gcc/cgraphunit.c:2275
0xab6c92 symbol_table::compile()
        ../../gcc/cgraphunit.c:2624
0xab6f06 symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.c:2717

We first create a constprop, so that following edge is cloned:

clonning: b/2->__builtin_free/14
# .MEM_19 = VDEF <.MEM_4(D)>
__builtin_memset (c_18(D), 32, _c.14_1);

and then after materialization we have following CFG:
  <bb 13> [local count: 1073741825]:
  if (1 != 0)
    goto <bb 14>; [41.48%]
  else
    goto <bb 15>; [58.52%]

  <bb 14> [local count: 445388109]:
  __builtin_memset (c_14(D), 32, _c.14_1);

then the if condition is folded away and we end up with:
<bb 3> [local count: 1073741825]:
_5 = 5;
_6 = 1;
_7 = 5;
_8 = 7;
_9 = 1;
_10 = 35;
_11 = 6;
_12 = 1;
_13 = 7;
__builtin_memset (c_14(D), 32, _c.14_1);
return;

and it's logical that count promotes from 445388109 -> 1073741825.
Is it something known? I consider it's related to fact the call is a call to
built-in.
Honza, Martin, any ideas?
>From gcc-bugs-return-630028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:49:54 2019
Return-Path: <gcc-bugs-return-630028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14291 invoked by alias); 21 Jan 2019 14:49:54 -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 14231 invoked by uid 48); 21 Jan 2019 14:49:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88934-4-jjgQsFNCGB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02837.txt.bz2
Content-length: 438

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-630029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:50:19 2019
Return-Path: <gcc-bugs-return-630029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17068 invoked by alias); 21 Jan 2019 14:50:19 -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 16998 invoked by uid 55); 21 Jan 2019 14:50:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88934] [9 Regression] ICE: verify_gimple failed (Error: mismatching comparison operand types)
Date: Mon, 21 Jan 2019 14:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88934-4-ZFWMriuyQq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88934-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: 2019-01/txt/msg02838.txt.bz2
Content-length: 713

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

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Jan 21 14:49:42 2019
New Revision: 268115

URL: https://gcc.gnu.org/viewcvs?rev=268115&root=gcc&view=rev
Log:
2019-01-21  Richard Biener  <rguenther@suse.de>

        PR tree-optimization/88934
        * tree-vect-slp.c (vect_mask_constant_operand_p): Always look
        at the possibly non-constant operand.
        (vect_get_constant_vectors): Adjust.

        * gfortran.dg/pr88934.f90: New testcase.

Added:
    trunk/gcc/testsuite/gfortran.dg/pr88934.f90
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-vect-slp.c
>From gcc-bugs-return-630030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:56:37 2019
Return-Path: <gcc-bugs-return-630030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123365 invoked by alias); 21 Jan 2019 14:56:37 -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 123289 invoked by uid 48); 21 Jan 2019 14:56:33 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Mon, 21 Jan 2019 14:56: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88928-4-oWoUiZENBp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg02839.txt.bz2
Content-length: 199

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

--- Comment #3 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Proposed fix: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01154.html
>From gcc-bugs-return-630031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:57:23 2019
Return-Path: <gcc-bugs-return-630031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9286 invoked by alias); 21 Jan 2019 14:57:23 -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 7234 invoked by uid 48); 21 Jan 2019 14:57:18 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88937] valgrind error in parse_has_include
Date: Mon, 21 Jan 2019 14:57: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-88937-4-tvvrccEaOr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88937-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88937-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: 2019-01/txt/msg02840.txt.bz2
Content-length: 666

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-21
                 CC|                            |marxin at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, I can fix it.
>From gcc-bugs-return-630033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:58:07 2019
Return-Path: <gcc-bugs-return-630033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26475 invoked by alias); 21 Jan 2019 14:58:07 -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 24162 invoked by uid 48); 21 Jan 2019 14:58:00 -0000
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] New: stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Mon, 21 Jan 2019 14:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matmal01 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88950-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: 2019-01/txt/msg02842.txt.bz2
Content-length: 3936

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

            Bug ID: 88950
           Summary: stack_protect_prologue can be reordered by sched1
                    around memory accesses
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: matmal01 at gcc dot gnu.org
  Target Milestone: ---

I've found a testcase where the stack protector code generated through
`-fstack-protector-all` doesn't actually protect anything.

With the following testcase

int foo (int a, int b, int c) {
        char buf[64];
        buf[a] = 1;
        buf[b] = c;

        // Just add something so that the assignments above have some
        // observable behaviour.
        int retval = 0;
        for (size_t i = 0; i < 32; i++)
        {
                retval += buf[i];
        }
        return retval;
}


When compiling for aarch64 with
gcc -fstack-protector-all -g -S stack-reorder.c  -o test.s -O3 -fdump-rtl-final
(with ~gcc (GCC) 9.0.0 20181214 (experimental)~)

We get an RTL dump on the final pass that has the snippet
(insn 8 21 130 (parallel [
            (set (mem/v/f/c:DI (plus:DI (reg/f:DI 31 sp)
                        (const_int 88 [0x58])) [1 D.4227+0 S8 A64])
                (unspec:DI [
                        (mem/v/f/c:DI (reg/f:DI 0 x0 [116]) [1
__stack_chk_guard+0 S8 A64])
                    ] UNSPEC_SP_SET))
            (set (reg:DI 1 x1 [141])
                (const_int 0 [0]))
        ]) "stack-reorder.c":3:31 1046 {stack_protect_set_di}
     (expr_list:REG_UNUSED (reg:DI 1 x1 [141])
        (nil)))
(note 130 8 117 (var_location b (entry_value:SI (reg:SI 1 x1 [ b ])))
NOTE_INSN_VAR_LOCATION)
(note 117 130 118 stack-reorder.c:4 NOTE_INSN_BEGIN_STMT)
(note 118 117 119 stack-reorder.c:5 NOTE_INSN_BEGIN_STMT)
(note 119 118 120 stack-reorder.c:6 NOTE_INSN_BEGIN_STMT)
(note 120 119 131 stack-reorder.c:10 NOTE_INSN_BEGIN_STMT)
(note 131 120 121 (var_location retval (const_int 0 [0]))
NOTE_INSN_VAR_LOCATION)
(note 121 131 144 stack-reorder.c:11 NOTE_INSN_BEGIN_STMT)
(note 144 121 122 0xffffb76fd960 NOTE_INSN_BLOCK_BEG)
(note 122 144 132 stack-reorder.c:11 NOTE_INSN_BEGIN_STMT)
(note 132 122 123 (var_location retval (nil)) NOTE_INSN_VAR_LOCATION)
(note 123 132 145 stack-reorder.c:13 NOTE_INSN_BEGIN_STMT)
(note 145 123 75 0xffffb76fd960 NOTE_INSN_BLOCK_END)
(insn:TI 75 145 133 (parallel [
            (set (reg:DI 1 x1 [137])
                (unspec:DI [
                        (mem/v/f/c:DI (plus:DI (reg/f:DI 31 sp)
                                (const_int 88 [0x58])) [1 D.4227+0 S8 A64])
                        (mem/v/f/c:DI (reg/f:DI 0 x0 [116]) [1
__stack_chk_guard+0 S8 A64])
                    ] UNSPEC_SP_TEST))
            (clobber (reg:DI 2 x2 [142]))
        ]) "stack-reorder.c":16:1 1048 {stack_protect_test_di}
     (expr_list:REG_DEAD (reg/f:DI 0 x0 [116])
        (expr_list:REG_UNUSED (reg:DI 2 x2 [142])
            (nil))))


In this snippet the stack protect set and test patterns are right next to each
other, causing the stack protector to essentially do nothing.
The RTL insns to set the two elements in `buf[]` are before this snippet.

The stack_protect_set and stack_protect_test patterns are put together in the
sched1 pass (as seen by the change in the RTL between the previous dump and
that
one).

I would like to know what is supposed to stop RTL from the stack_protect_set
pattern from being reordered around the code it protects like this?
I don't believe aarch64 is doing anything special here -- the stack protect set
and test patterns are very similar to those of other backends.

I recognise this is an unlikely pattern of code and that it doesn't present as
much of a security risk as things like calling memcpy or setting memory through
some sort of loop.
>From gcc-bugs-return-630032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:58:07 2019
Return-Path: <gcc-bugs-return-630032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26353 invoked by alias); 21 Jan 2019 14:58:06 -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 24498 invoked by uid 48); 21 Jan 2019 14:58:01 -0000
From: "sbence92 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88951] New: No fpermissive offerred on 'error: jump to case label'
Date: Mon, 21 Jan 2019 14:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sbence92 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88951-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: 2019-01/txt/msg02841.txt.bz2
Content-length: 712

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

            Bug ID: 88951
           Summary: No fpermissive offerred on 'error: jump to case label'
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sbence92 at gmail dot com
  Target Milestone: ---

r263551 removes the possibility to compile the below code with fpermissive.
This code has always been compiled by GCC, why remove the option now? This
breaks backward compatibility with some legacy code.


void f()
{
    switch(0)
    {
        int x = 0;
        case 0:
    }
}
>From gcc-bugs-return-630034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 14:59:04 2019
Return-Path: <gcc-bugs-return-630034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49736 invoked by alias); 21 Jan 2019 14:59:03 -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 46149 invoked by uid 48); 21 Jan 2019 14:58:57 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88948] [9 Regression] ICE in elimination_costs_in_insn, at reload1.c:3640 since r264148
Date: Mon, 21 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc component
Message-ID: <bug-88948-4-icmXTOo0M1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88948-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: 2019-01/txt/msg02843.txt.bz2
Content-length: 1550

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |law at gcc dot gnu.org
          Component|target                      |rtl-optimization

--- Comment #1 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Not a target problem.

It is RTL store motion pass that transforms:

(insn 19 18 20 4 (parallel [
            (set (mem/c:SI (symbol_ref:SI ("bar_arg") [flags 0x2]  <var_decl
0x7f68136f2b40 bar_arg>) [1 bar_arg+0 S4 A32])
                (fix:SI (reg:DF 89)))
            (clobber (scratch:XF))
        ]) "stdarg-3.c":63:7 156 {fix_truncsi_i387_fisttp}
     (expr_list:REG_DEAD (reg:DF 89)
        (nil)))

to an unrecognisable insn:

(insn 33 18 20 4 (set (reg:SI 93 [ bar_arg ])
        (fix:SI (reg:DF 89))) "stdarg-3.c":63:7 -1
     (expr_list:REG_DEAD (reg:DF 89)
        (nil)))

There is the following insn present in the i386.md:

(define_insn "fix_trunc<MODEF:mode><SWI48:mode>_sse"
  [(set (match_operand:SWI48 0 "register_operand" "=r,r")
        (fix:SWI48 (match_operand:MODEF 1 "nonimmediate_operand" "v,m")))]
  "SSE_FLOAT_MODE_P (<MODEF:MODE>mode)
   && (!TARGET_FISTTP || TARGET_SSE_MATH)"
  "%vcvtt<MODEF:ssemodesuffix>2si<SWI48:rex64suffix>\t{%1, %0|%0, %1}"

But with TARGET_FISTTP = 1 and TARGET_SSE_MATH = 0, as is the case with the
above testcase, it should be disabled.
>From gcc-bugs-return-630035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:00:42 2019
Return-Path: <gcc-bugs-return-630035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99848 invoked by alias); 21 Jan 2019 15:00:33 -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 82199 invoked by uid 48); 21 Jan 2019 15:00:00 -0000
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Mon, 21 Jan 2019 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matmal01 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88950-4-E1EJT2kKoX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88950-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: 2019-01/txt/msg02844.txt.bz2
Content-length: 235

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

--- Comment #1 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
Created attachment 45480
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45480&action=edit
Testcase
>From gcc-bugs-return-630036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:14:31 2019
Return-Path: <gcc-bugs-return-630036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97176 invoked by alias); 21 Jan 2019 15:14: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 97077 invoked by uid 48); 21 Jan 2019 15:14:17 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88734] [8 Regression] AArch64's ACLE intrinsics give an ICE instead of compile error when option mismatch.
Date: Mon, 21 Jan 2019 15:14: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: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88734-4-R0019qSLma@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88734-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: 2019-01/txt/msg02845.txt.bz2
Content-length: 175

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

--- Comment #10 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Thanks Jakub! testing hasn't shown any breakages.
>From gcc-bugs-return-630037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:17:48 2019
Return-Path: <gcc-bugs-return-630037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109224 invoked by alias); 21 Jan 2019 15:17:48 -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 109153 invoked by uid 48); 21 Jan 2019 15:17:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Mon, 21 Jan 2019 15:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88950-4-aRQnxX0rSw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88950-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: 2019-01/txt/msg02846.txt.bz2
Content-length: 507

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2019-01-21
     Ever confirmed|0                           |1

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
what architecture is this on?
>From gcc-bugs-return-630038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:18:37 2019
Return-Path: <gcc-bugs-return-630038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110724 invoked by alias); 21 Jan 2019 15:18:36 -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 110639 invoked by uid 48); 21 Jan 2019 15:18:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88951] [9 Regression] No fpermissive offerred on 'error: jump to case label'
Date: Mon, 21 Jan 2019 15:18: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone short_desc everconfirmed
Message-ID: <bug-88951-4-tErDSx5MQI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88951-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: 2019-01/txt/msg02847.txt.bz2
Content-length: 674

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
   Target Milestone|---                         |9.0
            Summary|No fpermissive offerred on  |[9 Regression] No
                   |'error: jump to case label' |fpermissive offerred on
                   |                            |'error: jump to case label'
     Ever confirmed|0                           |1
>From gcc-bugs-return-630039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:21:42 2019
Return-Path: <gcc-bugs-return-630039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114600 invoked by alias); 21 Jan 2019 15:21:41 -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 114513 invoked by uid 48); 21 Jan 2019 15:21:35 -0000
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Mon, 21 Jan 2019 15:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matmal01 at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-88950-4-t0s09ADbLF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88950-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: 2019-01/txt/msg02848.txt.bz2
Content-length: 185

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

--- Comment #3 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
aarch64 (both aarch64-none-linux-gnu and aarch64-none-elf)
>From gcc-bugs-return-630040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:26:09 2019
Return-Path: <gcc-bugs-return-630040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123322 invoked by alias); 21 Jan 2019 15:26:09 -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 123187 invoked by uid 48); 21 Jan 2019 15:26:03 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88931] Wrong __floattisf and __floattidf are selected in libgcc
Date: Mon, 21 Jan 2019 15:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_reconfirmed_on component cc dependson everconfirmed short_desc target_milestone
Message-ID: <bug-88931-4-6xGOmd3znu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88931-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: 2019-01/txt/msg02849.txt.bz2
Content-length: 1391

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86-64
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
          Component|c                           |libgcc
                 CC|                            |ubizjak at gmail dot com
         Depends on|34678                       |
     Ever confirmed|0                           |1
            Summary|Failed to convert int128 to |Wrong __floattisf and
                   |float/double with           |__floattidf are selected in
                   |round=FE_UPWARD/FE_TOWARDZE |libgcc
                   |RO                          |
   Target Milestone|---                         |9.0

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
On x86-64, wrong __floattisf and __floattidf are selected in libgcc.
They should come from soft-fp, not in libgcc2.c as

FSTYPE
FUNC (DWtype u)
{
  ...
}

which has no rounding mode support.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34678
[Bug 34678] Optimization generates incorrect code with -frounding-math option
(#pragma STDC FENV_ACCESS not implemented)
>From gcc-bugs-return-630041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:41:23 2019
Return-Path: <gcc-bugs-return-630041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99174 invoked by alias); 21 Jan 2019 15:41:23 -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 97982 invoked by uid 48); 21 Jan 2019 15:41:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88904] [9 Regression] Basic block incorrectly skipped in jump threading.
Date: Mon, 21 Jan 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88904-4-HEFORAQJZa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88904-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: 2019-01/txt/msg02850.txt.bz2
Content-length: 1580

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the right fix is something like:
--- gcc/cfgcleanup.c.jj 2019-01-01 12:37:19.147942300 +0100
+++ gcc/cfgcleanup.c    2019-01-21 16:35:00.737320489 +0100
@@ -338,6 +338,13 @@ thread_jump (edge e, basic_block b)
        insn != NEXT_INSN (BB_END (b)) && !failed;
        insn = NEXT_INSN (insn))
     {
+      /* cond2 must not mention any register that is not equal to the
+        former block.  Check this before processing that instruction,
+        as BB_END (b) could contain also clobbers.  */
+      if (insn == BB_END (b)
+         && mentions_nonequal_regs (cond2, nonequal))
+       goto failed_exit;
+
       if (INSN_P (insn))
        {
          rtx pat = PATTERN (insn);
@@ -362,11 +369,6 @@ thread_jump (edge e, basic_block b)
       goto failed_exit;
     }

-  /* cond2 must not mention any register that is not equal to the
-     former block.  */
-  if (mentions_nonequal_regs (cond2, nonequal))
-    goto failed_exit;
-
   EXECUTE_IF_SET_IN_REG_SET (nonequal, 0, i, rsi)
     goto failed_exit;

i.e. verify the condition before processing the second conditional jump,
because it is evaluated with the state of registers before the instruction,
rather than after it.
>From gcc-bugs-return-630042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 15:52:18 2019
Return-Path: <gcc-bugs-return-630042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7682 invoked by alias); 21 Jan 2019 15:52:17 -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 7271 invoked by uid 48); 21 Jan 2019 15:52:12 -0000
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88904] [9 Regression] Basic block incorrectly skipped in jump threading.
Date: Mon, 21 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: matmal01 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88904-4-ywvblWUQoT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88904-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: 2019-01/txt/msg02851.txt.bz2
Content-length: 264

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

--- Comment #3 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
I agree Jakub -- I've been testing a patch that does the same thing and
everything seems to be working (though my patch was not as neat).
>From gcc-bugs-return-630043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:07:31 2019
Return-Path: <gcc-bugs-return-630043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68339 invoked by alias); 21 Jan 2019 16:07:31 -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 68251 invoked by uid 48); 21 Jan 2019 16:07:23 -0000
From: "ssbssa at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88925] address of static string changes
Date: Mon, 21 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ssbssa at yahoo dot de
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88925-4-EqwSCtCMod@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88925-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88925-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: 2019-01/txt/msg02852.txt.bz2
Content-length: 741

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

--- Comment #2 from Domani Hannes <ssbssa at yahoo dot de> ---
(In reply to Richard Biener from comment #1)
> It works for me on x86_64-linux.  Note to get the desired behavior GCC
> relies on
> string-merging performed by the linker.
> 
> Can you elaborate on the host/target you compile for?

It's for x86_64-w64-mingw32.

I thought string-merging is only for the case when the same string literal is
used in multiple locations.
But here "Derived1" is only used once for typeDerived1, which
Derived1::getType() then returns.
So I never would have thought that Derived1::getType() could be different to
typeDerived1, which it is.

Am I depending on undefined behavior? If yes, why?
>From gcc-bugs-return-630044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:19:39 2019
Return-Path: <gcc-bugs-return-630044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101276 invoked by alias); 21 Jan 2019 16:19:39 -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 101159 invoked by uid 48); 21 Jan 2019 16:19:34 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 16:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-EkRBTSfERR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02853.txt.bz2
Content-length: 720

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

--- Comment #14 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
  I've checked cvtf_1.c generated code and I don't see additional fmov anymore.
 I guess it was fixed by an ira-costs.c change (a special consideration of
moves containing hard regs).  I think this PR is resolved (although the change
resulted in a new PR 88560 but it is a different story).

  If we want to improve the generated code size, it would be better to find a
small testcase from SPEC2006 showing what is wrong.  I understand it is a hard
work but otherwise we could only speculate what is going wrongly.  I don't
think that reverting the combiner change would be a solution.
>From gcc-bugs-return-630045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:27:01 2019
Return-Path: <gcc-bugs-return-630045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120693 invoked by alias); 21 Jan 2019 16:27:01 -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 119498 invoked by uid 55); 21 Jan 2019 16:26:55 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88936-4-TJDOPL1ni1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02854.txt.bz2
Content-length: 193

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

--- Comment #7 from Jan Hubicka <hubicka at ucw dot cz> ---
Hi,
there is ipa_reduced_postorder that will compute SCCs and store scc
index.
>From gcc-bugs-return-630046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:29:35 2019
Return-Path: <gcc-bugs-return-630046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9376 invoked by alias); 21 Jan 2019 16:29:34 -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 9250 invoked by uid 48); 21 Jan 2019 16:29:30 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88920] [9 regression] GCC is not configured to support amdgcn-unknown-amdhsa as offload target
Date: Mon, 21 Jan 2019 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ams at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88920-4-WPc87uwWuN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88920-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88920-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: 2019-01/txt/msg02855.txt.bz2
Content-length: 372

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

--- Comment #11 from Andrew Stubbs <ams at gcc dot gnu.org> ---
Created attachment 45481
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45481&action=edit
Cache test

This patch caches the result so that the (harmless) error message occurs only
once.

Is there a way to hide it in a higher verbosity level?
>From gcc-bugs-return-630047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:42:24 2019
Return-Path: <gcc-bugs-return-630047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94256 invoked by alias); 21 Jan 2019 16:42:24 -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 94044 invoked by uid 48); 21 Jan 2019 16:42:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88904] [9 Regression] Basic block incorrectly skipped in jump threading.
Date: Mon, 21 Jan 2019 16:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-88904-4-Tt4NHuCSvQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88904-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: 2019-01/txt/msg02856.txt.bz2
Content-length: 696

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-21
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45482
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45482&action=edit
gcc9-pr88904.patch

Full untested patch.
>From gcc-bugs-return-630048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:43:04 2019
Return-Path: <gcc-bugs-return-630048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95674 invoked by alias); 21 Jan 2019 16:43:03 -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 95550 invoked by uid 48); 21 Jan 2019 16:42:57 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/87835] nvptx offloading: libgomp.oacc-c-c++-common/asyncwait-1.c execution test intermittently fails at -O2
Date: Mon, 21 Jan 2019 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-87835-4-m0Kp57WcSp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87835-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: 2019-01/txt/msg02857.txt.bz2
Content-length: 10720

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

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
This minimized test-case (rewritten to avoid the kernels construct, by setting
the num_gangs as libgomp would have chosen it for kernels, and making the loop
a  gang loop):
...
/* { dg-do run } */
/* { dg-additional-options "-lcuda" { target openacc_nvidia_accel_selected } }
*/

#include <openacc.h>
#include <stdlib.h>
#include "cuda.h"

#include <stdio.h>

#define n 128

int
main (void)
{
  CUresult r;
  CUstream stream1;
  int N = n;
  int a[n];
  int b[n];
  int c[n];

  acc_init (acc_device_nvidia);

  r = cuStreamCreate (&stream1, CU_STREAM_NON_BLOCKING);
  if (r != CUDA_SUCCESS)
    {
      fprintf (stderr, "cuStreamCreate failed: %d\n", r);
      abort ();
    }

  acc_set_cuda_stream (1, stream1);

  for (int i = 0; i < n; i++)
    {
      a[i] = 3;
      c[i] = 0;
    }

#pragma acc data copy (a, b, c) copyin (N)
  {
#pragma acc parallel async (1)
    ;

#pragma acc parallel async (1) num_gangs (320)
#pragma loop gang
    for (int ii = 0; ii < N; ii++)
      c[ii] = (a[ii] + a[N - ii - 1]);

#pragma acc parallel async (1)
#pragma acc loop seq
    for (int ii = 0; ii < n; ii++)
      a[ii] = 6;

#pragma acc wait (1)
  }

  unsigned sum = 0;
  for (int i = 0; i < n; i++)
    if (c[i] != 6)
      {
        printf ("%d@%d ", c[i], i);
        sum++;
      }

  if (sum > 0)
    {
      printf ("mismatches: %u\n", sum);
      abort ();
    }

  return 0;
}
...

reproduces 100 out of 100 for me at -O2:
...
nr=100; sum=0; for n in $(seq 1 $nr); do ./run.sh ./asyncwait-1.exe ; if [ $?
-eq 0 ]; then sum=$(($sum + 1)); fi; done; echo ; echo "$sum/$nr"
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
15@125 27@126 39@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
12@125 24@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 30@127 mismatches: 3
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
21@126 30@127 mismatches: 2
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 24@127 mismatches: 2
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
15@125 24@126 39@127 mismatches: 3
Aborted (core dumped)
18@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 21@126 30@127 mismatches: 3
Aborted (core dumped)
18@125 27@126 39@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 21@126 36@127 mismatches: 3
Aborted (core dumped)
15@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
18@126 27@127 mismatches: 2
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
18@126 27@127 mismatches: 2
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
15@126 30@127 mismatches: 2
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 33@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
9@125 24@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
15@126 30@127 mismatches: 2
Aborted (core dumped)
15@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@126 21@127 mismatches: 2
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 33@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 30@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@124 15@125 27@126 42@127 mismatches: 4
Aborted (core dumped)
12@126 27@127 mismatches: 2
Aborted (core dumped)
12@125 21@126 36@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
18@126 33@127 mismatches: 2
Aborted (core dumped)
18@126 27@127 mismatches: 2
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 39@127 mismatches: 3
Aborted (core dumped)
15@126 30@127 mismatches: 2
Aborted (core dumped)
12@125 24@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
9@125 18@126 30@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 30@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 18@126 33@127 mismatches: 3
Aborted (core dumped)
15@125 27@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
12@125 24@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 21@126 33@127 mismatches: 3
Aborted (core dumped)
15@126 27@127 mismatches: 2
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
18@126 33@127 mismatches: 2
Aborted (core dumped)
18@126 30@127 mismatches: 2
Aborted (core dumped)
15@126 30@127 mismatches: 2
Aborted (core dumped)
12@125 21@126 36@127 mismatches: 3
Aborted (core dumped)
9@125 24@126 33@127 mismatches: 3
Aborted (core dumped)

0/100
...

This doesn't just look like an order of execution problem.

If we have the "a[ii] = 6" loop executed before the "c[ii] = (a[ii] + a[N - ii
- 1])" loop, still the maximum to be expected for each c element is 12. But we
see higher values here.

Reverting "[nvptx] Remove use of CUDA unified memory in libgomp" makes it pass
100 out of 100.

By forcing map_push to create a new map, rather than to reuse:
...
@@ -304,7 +304,7 @@ map_push (struct ptx_stream *s, size_t size)
   /* Each PTX stream requires a separate data region to store the              
      launch arguments for cuLaunchKernel.  Allocate a new                      
      cuda_map and push it to the end of the list.  */                          
-  if (s->map->active)                                                          
+  if (true)                                                                    
     {                                                                          
       map = cuda_map_create (size);                                            
...
the failure is turned into a duplicate of the more trivial PR88946 - "[nvptx,
openacc, libgomp] cuMemAlloc error for two empty asynchronous parallels".

So, the most likely cause for the error is that map_push returns a map that is
marked inactive, but in fact still in use. This could happen if a launch
completes and the event processing calls map_pop for the wrong map.

Using this debug patch:
...
diff --git a/libgomp/plugin/plugin-nvptx.c b/libgomp/plugin/plugin-nvptx.c
index dd2bcf3083f..158ba67d273 100644
--- a/libgomp/plugin/plugin-nvptx.c
+++ b/libgomp/plugin/plugin-nvptx.c
@@ -284,11 +284,13 @@ map_pop (struct ptx_stream *s)

   if (s->map->next == NULL)
     {
+      fprintf (stderr, "map_push makes map inactive: %p\n", s->map);
       s->map->active = false;
       return;
     }

   next = s->map->next;
+  fprintf (stderr, "map_push destroys map: %p\n", s->map);
   cuda_map_destroy (s->map);
   s->map = next;
 }
@@ -323,6 +325,7 @@ map_push (struct ptx_stream *s, size_t size)

   s->map = map;
   s->map->active = true;
+  fprintf (stderr, "map_push returns map: %p\n", s->map);

   return s->map->d;
 }
...

we see:
...
map_push returns map: 0x1e94260
map_push returns map: 0x1e913c0
map_push makes map inactive: 0x1e913c0
map_push returns map: 0x1e913c0
map_push makes map inactive: 0x1e913c0
map_push makes map inactive: 0x1e913c0
15@126 30@127 mismatches: 2
Aborted (core dumped)
...

That indeed seems wrong:

> map_push returns map: 0x1e94260
map for first parallel is allocated

> map_push returns map: 0x1e913c0
map for second parallel is allocated

> map_push makes map inactive: 0x1e913c0

First kernel finishes. This should not touch the map for the second parallel.


The root cause is that map_push is broken: after the second map_push, the map
list consist just of the second item pushed, the first item is dropped.
>From gcc-bugs-return-630049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:44:32 2019
Return-Path: <gcc-bugs-return-630049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106293 invoked by alias); 21 Jan 2019 16:44:31 -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 106064 invoked by uid 48); 21 Jan 2019 16:44:26 -0000
From: "christopher.leonard at abaco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/88952] New: [powerpc] asm input from C expression with type larger than GPRs loads wrong value
Date: Mon, 21 Jan 2019 16:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 4.2.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christopher.leonard at abaco dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88952-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: 2019-01/txt/msg02858.txt.bz2
Content-length: 2638

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

            Bug ID: 88952
           Summary: [powerpc] asm input from C expression with type larger
                    than GPRs loads wrong value
           Product: gcc
           Version: 4.2.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: inline-asm
          Assignee: unassigned at gcc dot gnu.org
          Reporter: christopher.leonard at abaco dot com
  Target Milestone: ---

When giving a C expression as input to an extended asm statement the wrong
value is loaded if the type happens to be 64-bit (with 32-bit powerpc target).
Happens regardless of optimization level, use of 'volatile'. Also happens in
compiler explorer with GCC 4.8.5 <https://godbolt.org/z/hZAEEy>.

This subtle behavior is not too hard to track down but will probably defy the
expectations of the programmer, and could be introduced into a program with
seemingly innocuous changes that result in the overall expression type being
larger. I assume this is a bug and not the intention of the input operand
feature. If this is the intended functionality I would suggest adding a warning
for this situation.

Source "ex.c":
    void bad_asm(void)
    {
        asm volatile ("stw %0, 50(0)" : :"r"(20ull));
    }

Build command:
    /opt/eldk/4.2/usr/ppc-linux/bin/gcc -mregnames -O3 -c -o ex.o ex.c

Disassembly:
    ex.o:     file format elf32-powerpc

    Disassembly of section .text:

    00000000 <bad_asm>:
       0:       39 20 00 00     li      r9,0
       4:       39 40 00 14     li      r10,20
       8:       91 20 00 32     stw     r9,50(0)
       c:       4e 80 00 20     blr

Output of gcc -v:
    Reading specs from
/opt/eldk/4.2/usr/bin/../lib/gcc/powerpc-linux/4.2.2/specs
    Target: powerpc-linux
    Configured with:
/opt/eldk/build/ppc-2008-04-01/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/gcc-4.2.2/configure
--target=powerpc-linux --host=i686-host_pc-linux-gnu
--prefix=/var/tmp/eldk.UZpAG7/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux
--disable-hosted-libstdcxx
--with-headers=/var/tmp/eldk.UZpAG7/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/powerpc-linux/include
--with-local-prefix=/var/tmp/eldk.UZpAG7/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/powerpc-linux/powerpc-linux
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit
--enable-languages=c,c++,java --enable-shared --enable-c99 --enable-long-long
--without-x
    Thread model: posix
    gcc version 4.2.2
>From gcc-bugs-return-630050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:46:33 2019
Return-Path: <gcc-bugs-return-630050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4761 invoked by alias); 21 Jan 2019 16:46:33 -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 4673 invoked by uid 48); 21 Jan 2019 16:46:29 -0000
From: "Jan.Kossmann at hpi dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] New: Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Mon, 21 Jan 2019 16:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Jan.Kossmann at hpi dot de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88953-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: 2019-01/txt/msg02859.txt.bz2
Content-length: 1225

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

            Bug ID: 88953
           Summary: Unrecognizable insn on architecture zEC12 with
                    boost::bimap
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Jan.Kossmann at hpi dot de
  Target Milestone: ---

When compiling with gcc 8.2.0 (shipped with Ubuntu) the flags -O3 and
-march=native on Ubuntu 18.04.1 on IBM/S390, boost version: 1.65.1.0, I get the
following output:

g++ -O3 -march=native -o test.cpp.o  test.cpp
test.cpp: In function â€˜(static initializers for test.cpp)â€™:
test.cpp:20:1: error: unrecognizable insn:
 }
 ^
(insn 2167 2166 2168 494 (set (reg:V2DI 1019)
        (vec_duplicate:V2DI (const:DI (plus:DI (symbol_ref:DI
("_ZN7opossum4pctsB5cxx11E") [flags 0x2] <var_decl 0x3ff761ab7e0 pcts>)
                    (const_int 32 [0x20])))))
"/usr/include/boost/bimap/container_adaptor/detail/functor_bag.hpp":74 -1
     (nil))
during RTL pass: vregs
test.cpp:20:1: internal compiler error: in extract_insn, at recog.c:2304
>From gcc-bugs-return-630052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:49:21 2019
Return-Path: <gcc-bugs-return-630052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12008 invoked by alias); 21 Jan 2019 16:49: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 11224 invoked by uid 48); 21 Jan 2019 16:49:15 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] New: __attribute__((noplt)) doesn't work with function pointers
Date: Mon, 21 Jan 2019 16:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter dependson target_milestone cf_gcctarget
Message-ID: <bug-88954-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: 2019-01/txt/msg02861.txt.bz2
Content-length: 2255

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

            Bug ID: 88954
           Summary: __attribute__((noplt)) doesn't work with function
                    pointers
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
        Depends on: 67400
  Target Milestone: ---
            Target: i386, x86-64

[hjl@gnu-cfl-1 noplt-3]$ make clean
rm -f *.o *.so *.s
[hjl@gnu-cfl-1 noplt-3]$ cat main.c 
void f_noplt(void) __attribute__((noplt));
void (*p_noplt)(void) = f_noplt;
void g(void (*)(void));

int main()
{
        g(p_noplt); // lazy: linker sets p_noplt to PLT address
        g(f_noplt); // lazy: linker sets mov immediate to PLT address
        f_noplt();  // non-lazy
        return 0;
}
[hjl@gnu-cfl-1 noplt-3]$ cat lib.c 
__attribute__((noplt)) void f_noplt(void) {}
void g(void p(void)) {p();}
[hjl@gnu-cfl-1 noplt-3]$ make CC=gcc
gcc -O2 -fno-pic    -c -o main.o main.c
gcc -O2 -fno-pic  -fPIC   -c -o lib.o lib.c
gcc  -shared -o lib.so lib.o
gcc -no-pie -o x main.o lib.so -Wl,-R,.
./x
[hjl@gnu-cfl-1 noplt-3]$ readelf -rW x

Relocation section '.rela.dyn' at offset 0x4c8 contains 3 entries:
    Offset             Info             Type               Symbol's Value 
Symbol's Name + Addend
0000000000403fe8  0000000400000006 R_X86_64_GLOB_DAT      0000000000401030
f_noplt + 0
0000000000403ff0  0000000100000006 R_X86_64_GLOB_DAT      0000000000000000
__libc_start_main@GLIBC_2.2.5 + 0
0000000000403ff8  0000000200000006 R_X86_64_GLOB_DAT      0000000000000000
__gmon_start__ + 0

Relocation section '.rela.plt' at offset 0x510 contains 2 entries:
    Offset             Info             Type               Symbol's Value 
Symbol's Name + Addend
0000000000404018  0000000400000007 R_X86_64_JUMP_SLOT     0000000000401030
f_noplt + 0

This dynamic relocation shouldn't be here.

0000000000404020  0000000300000007 R_X86_64_JUMP_SLOT     0000000000000000 g +
0
[hjl@gnu-cfl-1 noplt-3]$


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67400
[Bug 67400] -fno-plt doesn't work with function pointers
>From gcc-bugs-return-630053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:49:42 2019
Return-Path: <gcc-bugs-return-630053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14183 invoked by alias); 21 Jan 2019 16:49:41 -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 13718 invoked by uid 48); 21 Jan 2019 16:49:36 -0000
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88897] Bogus maybe-uninitialized warning on class field
Date: Mon, 21 Jan 2019 16:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rafael at espindo dot la
X-Bugzilla-Status: UNCONFIRMED
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-88897-4-nNB6c98fbf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88897-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88897-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: 2019-01/txt/msg02862.txt.bz2
Content-length: 478

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

Rafael Avila de Espindola <rafael at espindo dot la> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenther at suse dot de

--- Comment #5 from Rafael Avila de Espindola <rafael at espindo dot la> ---
This is a regression introduced by 4d2b9d1e3c794a05c00708035519290e920768e8.
>From gcc-bugs-return-630051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:49:08 2019
Return-Path: <gcc-bugs-return-630051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10168 invoked by alias); 21 Jan 2019 16:49:07 -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 9499 invoked by uid 48); 21 Jan 2019 16:49:00 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/88952] [powerpc] asm input from C expression with type larger than GPRs loads wrong value
Date: Mon, 21 Jan 2019 16:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 4.2.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
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: bug_status resolution
Message-ID: <bug-88952-4-fKZxYu1dC5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg02860.txt.bz2
Content-length: 456

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

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> ---
64bit is a register pair: hi:lo .
>From gcc-bugs-return-630054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:53:36 2019
Return-Path: <gcc-bugs-return-630054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50979 invoked by alias); 21 Jan 2019 16:53:36 -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 50829 invoked by uid 48); 21 Jan 2019 16:53:32 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88560] [9 Regression] armv8_2-fp16-move-1.c and related regressions after r266385
Date: Mon, 21 Jan 2019 16:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88560-4-zaBfosUc8J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88560-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: 2019-01/txt/msg02863.txt.bz2
Content-length: 1688

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

--- Comment #7 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Wilco from comment #6)
> (In reply to Vladimir Makarov from comment #5)
> > We have too many tests checking expected generated code.  We should more
> > focus on overall effect of the change.  SPEC would be a good criterium
> > although it is hard to check SPEC for each patch.
> > 
> > I've checked the generated code of arm8_2-fp16-move-1.c and found that in
> > most cases GCC generates better code with the patch:
> > 
> > @@ -80,7 +80,6 @@ test_load_store_1:
> >         @ frame_needed = 0, uses_anonymous_args = 0
> >         @ link register save eliminated.
> >         lsl     r1, r1, #1
> > -       vmov.f16        s0, r3  @ __fp16
> >         ldrh    r3, [r2, r1]    @ __fp16
> >         strh    r3, [r0, r1]    @ __fp16
> >         bx      lr
> 
> When I tested it, this test added that vmov, not removed it - see comment #2.

I've just checked the generated code again by using

./xgcc -B.
/home/vmakarov/build1/trunk/gcc/gcc/testsuite/gcc.target/arm/armv8_2-fp16-move-1.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O2 -mfpu=fp-armv8 -march=armv8.2-a+fp16
-mfloat-abi=hard -ffat-lto-objects -fno-ident -o b1.s -S

The code is 

test_load_store_1:
        @ args = 0, pretend = 0, frame = 0
        @ frame_needed = 0, uses_anonymous_args = 0
        @ link register save eliminated.
        lsl     r1, r1, #1
        ldrh    r3, [r2, r1]    @ __fp16
        strh    r3, [r0, r1]    @ __fp16
        bx      lr

GCC revision is r267848 as of Jan 11,2019.
>From gcc-bugs-return-630055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 16:53:55 2019
Return-Path: <gcc-bugs-return-630055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51971 invoked by alias); 21 Jan 2019 16:53:54 -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 51714 invoked by uid 48); 21 Jan 2019 16:53:49 -0000
From: "christopher.leonard at abaco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/88952] [powerpc] asm input from C expression with type larger than GPRs loads wrong value
Date: Mon, 21 Jan 2019 16:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 4.2.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christopher.leonard at abaco 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-88952-4-QtQHMJOqlT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg02864.txt.bz2
Content-length: 242

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

--- Comment #2 from Christopher Leonard <christopher.leonard at abaco dot com> ---
Surely then in the example if r9 is loaded with high and r10 with low then %0
should be r10, not r9?
>From gcc-bugs-return-630056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:04:59 2019
Return-Path: <gcc-bugs-return-630056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89684 invoked by alias); 21 Jan 2019 17:04:58 -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 89551 invoked by uid 48); 21 Jan 2019 17:04:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Mon, 21 Jan 2019 17:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88953-4-KPpPowmIKp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88953-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: 2019-01/txt/msg02865.txt.bz2
Content-length: 635

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |krebbel at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Please attach preprocessed source and for -march=native you need to note what
it expands to (e.g. use -save-temps -v and mention the cc1plus command line and
attach test.ii).
>From gcc-bugs-return-630057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:12:48 2019
Return-Path: <gcc-bugs-return-630057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26839 invoked by alias); 21 Jan 2019 17:12:48 -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 26784 invoked by uid 55); 21 Jan 2019 17:12:43 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Mon, 21 Jan 2019 17:12: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88928-4-WaHBAOERh0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg02866.txt.bz2
Content-length: 1143

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

--- Comment #4 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Author: edlinger
Date: Mon Jan 21 17:12:09 2019
New Revision: 268118

URL: https://gcc.gnu.org/viewcvs?rev=268118&root=gcc&view=rev
Log:
2019-01-21  Bernd Edlinger  <bernd.edlinger@hotmail.de>

        PR c/88928
        * c-warn.c (check_alignment_of_packed_member): Add a boolean parameter
        for rvalue context.  Handle rvalues correctly.  Use min_align_of_type
        instead of TYPE_ALIGN.
        (check_address_or_pointer_of_packed_member): Handle rvalues coorrectly.
        Use min_align_of_type instead of TYPE_ALIGN_UNIT.  Check for NULL
        pointer from TYPE_STUB_DECL.

testsuite:
2019-01-21  Bernd Edlinger  <bernd.edlinger@hotmail.de>

        PR c/88928
        * c-c++-common/Waddress-of-packed-member-1.c: New test case.
        * gcc.dg/pr88928.c: New test case.

Added:
    trunk/gcc/testsuite/c-c++-common/Waddress-of-packed-member-1.c
    trunk/gcc/testsuite/gcc.dg/pr88928.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/c-family/c-warn.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:14:39 2019
Return-Path: <gcc-bugs-return-630058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31573 invoked by alias); 21 Jan 2019 17:14:39 -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 31503 invoked by uid 48); 21 Jan 2019 17:14:34 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Mon, 21 Jan 2019 17:14: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88928-4-qyNEiNOViV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg02867.txt.bz2
Content-length: 462

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

Bernd Edlinger <edlinger at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Fixed on trunk, thanks for reporting!
>From gcc-bugs-return-630059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:16:24 2019
Return-Path: <gcc-bugs-return-630059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34458 invoked by alias); 21 Jan 2019 17:16:24 -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 33962 invoked by uid 48); 21 Jan 2019 17:16:14 -0000
From: "christopher.leonard at abaco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/88952] [powerpc] asm input from C expression with type larger than GPRs loads wrong value
Date: Mon, 21 Jan 2019 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 4.2.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christopher.leonard at abaco 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-88952-4-oTwzueRe8i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg02868.txt.bz2
Content-length: 309

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

--- Comment #3 from Christopher Leonard <christopher.leonard at abaco dot com> ---
I understand it has to split it, the problem is that %0 defaults to the
register holding the most-significant part of the integer. Is this really the
desired behavior?
>From gcc-bugs-return-630060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:19:54 2019
Return-Path: <gcc-bugs-return-630060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125939 invoked by alias); 21 Jan 2019 17:19:53 -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 125145 invoked by uid 48); 21 Jan 2019 17:19:47 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Mon, 21 Jan 2019 17:19: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: cf_gcctarget bug_status keywords cf_reconfirmed_on component resolution everconfirmed short_desc
Message-ID: <bug-88952-4-P0dJNpPsTj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg02869.txt.bz2
Content-length: 1392

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |powerpc-*-*
             Status|RESOLVED                    |NEW
           Keywords|                            |documentation
   Last reconfirmed|                            |2019-01-21
          Component|inline-asm                  |target
         Resolution|INVALID                     |---
     Ever confirmed|0                           |1
            Summary|[powerpc] asm input from C  |The asm operator modifiers
                   |expression with type larger |for rs6000 should be
                   |than GPRs loads wrong value |documented like they are
                   |                            |for x86

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Christopher Leonard from comment #2)
> Surely then in the example if r9 is loaded with high and r10 with low then
> %0 should be r10, not r9?

%0 represents the first register which in this case is r9.  The pair is r9:r10
to get the low part use %L0 .

Really this should be documented like they are for x86:
https://gcc.gnu.org/onlinedocs/gcc-8.2.0/gcc/Extended-Asm.html#x86-Operand-Modifiers
>From gcc-bugs-return-630061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:27:27 2019
Return-Path: <gcc-bugs-return-630061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40911 invoked by alias); 21 Jan 2019 17:27:27 -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 40821 invoked by uid 48); 21 Jan 2019 17:27:23 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88955] New: transparent_union for vector types not accepted
Date: Mon, 21 Jan 2019 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88955-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: 2019-01/txt/msg02870.txt.bz2
Content-length: 1222

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

            Bug ID: 88955
           Summary: transparent_union for vector types not accepted
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: amonakov at gcc dot gnu.org
  Target Milestone: ---

GCC (and Clang) rejects an attempt to create a transparent union corresponding
to an SSE register:

typedef unsigned long u64x2 __attribute__ ((vector_size (16)));

typedef union
__attribute__((transparent_union))
{
        u64x2   u64;
} v128;

The diagnostic is not very clear about the reason:

union.i:3:9: warning: union cannot be made transparent

Looking in gdb, it appears that the union has mode TI, while its TYPE_FIELDS
has V2DI mode.

Adding a dummy __int128 field makes GCC accept the code (but such workaround
won't work for wider vectors, or on 32-bit).

The intended usecase for this is a vector union type for easier interop between
Intel intrinsics and user code written with generic vectors, as suggested by
Richard in https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01186.html
>From gcc-bugs-return-630062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:27:38 2019
Return-Path: <gcc-bugs-return-630062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41727 invoked by alias); 21 Jan 2019 17: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 41629 invoked by uid 48); 21 Jan 2019 17:27:34 -0000
From: "Jan.Kossmann at hpi dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Mon, 21 Jan 2019 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Jan.Kossmann at hpi dot de
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-88953-4-neREhzVd6c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88953-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: 2019-01/txt/msg02871.txt.bz2
Content-length: 509

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

--- Comment #2 from Jan Kossmann <Jan.Kossmann at hpi dot de> ---
Created attachment 45483
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45483&action=edit
Preprocessed file and minimal cpp example

This archive contains the preprocessed *.ii file, a .cpp and .hpp file. I was
unable to reduce the file size of the *.ii file below 1000 KB because I had to
include a boost header. However, the .cpp and .hpp files are combined only 10
LOC.
>From gcc-bugs-return-630063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:37:18 2019
Return-Path: <gcc-bugs-return-630063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62299 invoked by alias); 21 Jan 2019 17:37:18 -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 62178 invoked by uid 48); 21 Jan 2019 17:37:12 -0000
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Mon, 21 Jan 2019 17:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: timshen 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:
Message-ID: <bug-88947-4-gtjvUtsPrr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg02872.txt.bz2
Content-length: 540

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

--- Comment #3 from Tim Shen <timshen at gcc dot gnu.org> ---
Thanks for reporting Tomalak.

Yes, I agree that "match from the first character" should be expressable in the
public interface, preferrably regex_search() with "^...". In fact, internally
regex_search is implemented in terms of such semantic.

As for other forms like "(^...)", or "(^abc|^xyz)", I'm sure we can go down the
rabbit hole and support more of them, but IMO the gain is marginal if "^..." is
supported.
>From gcc-bugs-return-630064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:42:37 2019
Return-Path: <gcc-bugs-return-630064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73450 invoked by alias); 21 Jan 2019 17:42:36 -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 73407 invoked by uid 48); 21 Jan 2019 17:42:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88949] ICE in expand_expr_real_1, at expr.c:10001 with -fopenmp
Date: Mon, 21 Jan 2019 17:42: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: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88949-4-ssHwaQaPr9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88949-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: 2019-01/txt/msg02873.txt.bz2
Content-length: 448

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As it works with -DMETHOD -fopenmp, but doesn't with -fopenmp, it must be the
cdtor copying in the FE that breaks this.

struct A {
  int a;
  A (int x) : a (x)
#ifdef METHOD
  {}
  void foo ()
#endif
  {
#pragma omp parallel firstprivate (a)
    --a;
  }
};

int c;

int
main ()
{
  A d(c);
#ifdef METHOD
  d.foo ();
#endif
}
>From gcc-bugs-return-630065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:52:12 2019
Return-Path: <gcc-bugs-return-630065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112903 invoked by alias); 21 Jan 2019 17:52:11 -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 112799 invoked by uid 48); 21 Jan 2019 17:52:06 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87763-4-aYrSmE3Hwp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02874.txt.bz2
Content-length: 927

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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot gnu.org

--- Comment #15 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
>   If we want to improve the generated code size, it would be better to find
> a small testcase from SPEC2006 showing what is wrong.  I understand it is a
> hard work but otherwise we could only speculate what is going wrongly.  I
> don't think that reverting the combiner change would be a solution.

Maybe not reverting, but at least making it conditional per architecture by
means of a hook.  We have hooks for many obscure issues so having one for this
rather visible issue (at least on some architectures) is in order IMO.
>From gcc-bugs-return-630066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:56:27 2019
Return-Path: <gcc-bugs-return-630066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120656 invoked by alias); 21 Jan 2019 17:56:27 -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 120540 invoked by uid 48); 21 Jan 2019 17:56:22 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88956] New: [9 Regression] ICE: Floating point exception
Date: Mon, 21 Jan 2019 17:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88956-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: 2019-01/txt/msg02875.txt.bz2
Content-length: 1831

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

            Bug ID: 88956
           Summary: [9 Regression] ICE: Floating point exception
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Changed between 20180708 and 20180722 :


$ cat z1.c
const char a[0][0] = { };
char b[3];
void f (void)
{
  __builtin_memcpy (b, a, 2);
}


$ gcc-9-20180708 -c z1.c
$
$ gcc-9-20190120 -c z1.c
during GIMPLE pass: lower
z1.c: In function 'f':
z1.c:3:6: internal compiler error: Floating point exception
    3 | void f (void)
      |      ^
0xa8afef crash_signal
        ../../gcc/toplev.c:326
0x837abc fold_array_ctor_reference
        ../../gcc/gimple-fold.c:6732
0x837abc fold_ctor_reference(tree_node*, tree_node*, poly_int<1u, unsigned
long> const&, poly_int<1u, unsigned long> const&, tree_node*, unsigned long*)
        ../../gcc/gimple-fold.c:6925
0x7ccb38 string_constant(tree_node*, tree_node**, tree_node**, tree_node**)
        ../../gcc/expr.c:11533
0x6b11ee c_strlen(tree_node*, int, c_strlen_data*, unsigned int)
        ../../gcc/builtins.c:676
0x83c2c0 gimple_fold_builtin_memory_op
        ../../gcc/gimple-fold.c:760
0x83dbbf gimple_fold_builtin
        ../../gcc/gimple-fold.c:3849
0x8407db gimple_fold_call
        ../../gcc/gimple-fold.c:4354
0x8407db fold_stmt_1
        ../../gcc/gimple-fold.c:5019
0x1197021 lower_stmt
        ../../gcc/gimple-low.c:387
0x1197021 lower_sequence
        ../../gcc/gimple-low.c:217
0x1196e88 lower_gimple_bind
        ../../gcc/gimple-low.c:473
0x1197bb1 lower_function_body
        ../../gcc/gimple-low.c:110
0x1197bb1 execute
        ../../gcc/gimple-low.c:195
>From gcc-bugs-return-630068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:59:47 2019
Return-Path: <gcc-bugs-return-630068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50372 invoked by alias); 21 Jan 2019 17:59: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 49227 invoked by uid 48); 21 Jan 2019 17:59:41 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88957] New: ICE: Segmentation fault in tree_could_trap_p, at tree-eh.c:2672
Date: Mon, 21 Jan 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-88957-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: 2019-01/txt/msg02877.txt.bz2
Content-length: 1712

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

            Bug ID: 88957
           Summary: ICE: Segmentation fault in tree_could_trap_p, at
                    tree-eh.c:2672
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

With option -fsanitize=undefined at -O[23] :


$ cat z1.d
int f (const int[4] x)
{
    int sum = 0;
    foreach (i; x) sum += i;
    return sum;
}
void main ()
{
    import core.simd : int4;
    f(int4.init.array);
}


$ gdc-9-20190120 -c z1.d -O2
$
$ gdc-9-20190120 -c z1.d -O2 -fsanitize=undefined
during RTL pass: expand
z1.d: In function 'D main':
z1.d:10:5: internal compiler error: Segmentation fault
   10 |     f(int4.init.array);
      |     ^
0xb821cf crash_signal
        ../../gcc/toplev.c:326
0xbd18d3 tree_could_trap_p(tree_node*)
        ../../gcc/tree-eh.c:2672
0x8a09e4 set_mem_attributes_minus_bitpos(rtx_def*, tree_node*, int,
poly_int<1u, long>)
        ../../gcc/emit-rtl.c:2016
0x8c9c54 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
        ../../gcc/expr.c:10327
0x8d47f6 store_expr(tree_node*, rtx_def*, int, bool, bool)
        ../../gcc/expr.c:5648
0x8d553e expand_assignment(tree_node*, tree_node*, bool)
        ../../gcc/expr.c:5431
0x7d0f28 expand_gimple_stmt_1
        ../../gcc/cfgexpand.c:3752
0x7d0f28 expand_gimple_stmt
        ../../gcc/cfgexpand.c:3850
0x7d3167 expand_gimple_basic_block
        ../../gcc/cfgexpand.c:5886
0x7d87a6 execute
        ../../gcc/cfgexpand.c:6509
>From gcc-bugs-return-630067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 17:59:42 2019
Return-Path: <gcc-bugs-return-630067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49290 invoked by alias); 21 Jan 2019 17:59:42 -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 46349 invoked by uid 48); 21 Jan 2019 17:59:37 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-QqcXmNCt5N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02876.txt.bz2
Content-length: 1645

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

--- Comment #16 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Wilco from comment #13)
> (In reply to Segher Boessenkool from comment #12)
> > Before the change combine forwarded all argument (etc.) hard registers
> > wherever
> > it could, doing part of RA's job (and doing a lousy job of it).  If after the
> > change it no longer two ranges, than a) that is a good decision, or b) there
> > is
> > some bug in RA.
> 
> I think it's important not to conflate avoiding increasing live ranges of
> hard registers and inserting redundant extra moves which cannot be
> optimized. The former unconditionally looks like a good idea, however I
> can't see any valid reasoning for the latter.

Good thing then that that is not what is done!

> Basically we now always get 2 moves for every physical register,

Huh?

The combiner inserts an extra move, yes, but it will always optimise it
away again.  Unless something in your target code prevents that?

(The extra moves are needed because combining a move with some compare or
similar can result in a two-output insn, like adds on arm for example).

> and this seems to thwart register preferencing.
> 
> > 0.05% code size is nothing, most other biggish changes have a much bigger
> > effect.
> 
> Compiler optimization is all about making many small changes which add up to
> a large improvement. This is actually quite significant given practically
> all code is affected negatively.

No, 0.05% code size is nothing.  _Especially_ where accompanied by a run time
improvement.  And it fixes some ICEs, too.
>From gcc-bugs-return-630070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:03:00 2019
Return-Path: <gcc-bugs-return-630070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71850 invoked by alias); 21 Jan 2019 18:02:59 -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 71224 invoked by uid 48); 21 Jan 2019 18:02:53 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88958] ICE in walk_aliased_vdefs_1, at tree-ssa-alias.c:2887
Date: Mon, 21 Jan 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88958-4-AtR85ioL40@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88958-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: 2019-01/txt/msg02879.txt.bz2
Content-length: 905

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

--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---

$ gdc-9-20190120 -c z1.d -O0
$
$ gdc-9-20190120 -c z1.d -O1
during GIMPLE pass: fre
In function 'h':
d21: internal compiler error: in copy_reference_ops_from_ref, at
tree-ssa-sccvn.c:976
0xce83a5 copy_reference_ops_from_ref
        ../../gcc/tree-ssa-sccvn.c:976
0xce90a5 valueize_shared_reference_ops_from_ref
        ../../gcc/tree-ssa-sccvn.c:1626
0xcea5a9 vn_reference_lookup(tree_node*, tree_node*, vn_lookup_kind,
vn_reference_s**, bool)
        ../../gcc/tree-ssa-sccvn.c:2708
0xcf16f9 visit_reference_op_load
        ../../gcc/tree-ssa-sccvn.c:4067
0xcf16f9 visit_stmt
        ../../gcc/tree-ssa-sccvn.c:4485
0xcf2aeb process_bb
        ../../gcc/tree-ssa-sccvn.c:6055
0xcf3eff do_rpo_vn
        ../../gcc/tree-ssa-sccvn.c:6662
0xcf4e2c execute
        ../../gcc/tree-ssa-sccvn.c:6797
>From gcc-bugs-return-630069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:02:26 2019
Return-Path: <gcc-bugs-return-630069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69567 invoked by alias); 21 Jan 2019 18:02:25 -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 69500 invoked by uid 48); 21 Jan 2019 18:02:21 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88958] New: ICE in walk_aliased_vdefs_1, at tree-ssa-alias.c:2887
Date: Mon, 21 Jan 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-88958-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: 2019-01/txt/msg02878.txt.bz2
Content-length: 1199

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

            Bug ID: 88958
           Summary: ICE in walk_aliased_vdefs_1, at tree-ssa-alias.c:2887
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

With following snippet :


$ cat z1.d
void f(int) {}
void g(...) {}
void h()
{
    g(*&f);
}


$ gdc-9-20190120 -c z1.d
$
$ gdc-9-20190120 -c z1.d -O0 -Wextra
during GIMPLE pass: *early_warn_uninitialized
In function 'h':
d21: internal compiler error: Segmentation fault
0xb821cf crash_signal
        ../../gcc/toplev.c:326
0xc4f63c walk_aliased_vdefs_1
        ../../gcc/tree-ssa-alias.c:2887
0xc4f7e1 walk_aliased_vdefs(ao_ref*, tree_node*, bool (*)(ao_ref*, tree_node*,
void*), void*, bitmap_head**, bool*, unsigned int)
        ../../gcc/tree-ssa-alias.c:2945
0xd34d04 warn_uninitialized_vars
        ../../gcc/tree-ssa-uninit.c:342
0xd34f80 execute_early_warn_uninitialized
        ../../gcc/tree-ssa-uninit.c:2736
0xd34f80 execute
        ../../gcc/tree-ssa-uninit.c:2771
>From gcc-bugs-return-630071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:23:43 2019
Return-Path: <gcc-bugs-return-630071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102042 invoked by alias); 21 Jan 2019 18:23:42 -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 101935 invoked by uid 48); 21 Jan 2019 18:23:36 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88959] New: Unnecessary xor before bsf/tzcnt
Date: Mon, 21 Jan 2019 18:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88959-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: 2019-01/txt/msg02880.txt.bz2
Content-length: 883

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

            Bug ID: 88959
           Summary: Unnecessary xor before bsf/tzcnt
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bugzilla@poradnik-webmastera.com
  Target Milestone: ---

[code]
int test(int x)
{
    return __builtin_ctz(x);
}
[/code]

gcc 4.9.1 with -O3 produces this:

[asm]
test(int):
  rep bsf eax, edi
  ret
[/asm]

And this with -O3 -mbmi:

[asm]
test(int):
  tzcnt eax, edi
  ret
[/asm]

gcc 4.9.2 and newer (including gcc 9) produces this for both cases:

[asm]
test(int):
  xor eax, eax
  rep bsf eax, edi
  ret
[/asm]

[asm]
test(int):
  xor eax, eax
  tzcnt eax, edi
  ret
[/asm]

This extra xor instruction is not needed here.
>From gcc-bugs-return-630072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:38:44 2019
Return-Path: <gcc-bugs-return-630072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31525 invoked by alias); 21 Jan 2019 18:38:43 -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 31444 invoked by uid 48); 21 Jan 2019 18:38:39 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87038] diagnostics: Have -Wjump-misses-init be enabled by -Wall or -Wextra
Date: Mon, 21 Jan 2019 18:38: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: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager 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: short_desc
Message-ID: <bug-87038-4-J9JmiAdjVx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87038-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87038-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: 2019-01/txt/msg02881.txt.bz2
Content-length: 859

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

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|diagnostics: Please add     |diagnostics: Have
                   |warning for jumping over    |-Wjump-misses-init be
                   |initializers with           |enabled by -Wall or -Wextra
                   |switch/case in C mode       |

--- Comment #22 from Eric Gallager <egallager at gcc dot gnu.org> ---
Retitling to better reflect what the debate is actually about.

(In reply to Harald van Dijk from comment #21)
> Since -Wjump-misses-init triggers too often for commonly used C patterns,
> I do not think it is appropriate to include it in -Wall. 

OK, so what about -Wextra then?
>From gcc-bugs-return-630073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:44:46 2019
Return-Path: <gcc-bugs-return-630073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49447 invoked by alias); 21 Jan 2019 18:44: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 49362 invoked by uid 48); 21 Jan 2019 18:44:43 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88501] Improve suggested alternative to be closer to typo
Date: Mon, 21 Jan 2019 18:44: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: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-88501-4-XGIVqGcHlA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88501-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88501-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: 2019-01/txt/msg02882.txt.bz2
Content-length: 598

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

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=88944

--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #9)
> That's only relevant for C, not C++, so should be a separate bug.

It's now bug 88944
>From gcc-bugs-return-630074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:46:40 2019
Return-Path: <gcc-bugs-return-630074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58220 invoked by alias); 21 Jan 2019 18:46:40 -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 58184 invoked by uid 48); 21 Jan 2019 18:46:36 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88959] Unnecessary xor before bsf/tzcnt
Date: Mon, 21 Jan 2019 18:46: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.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88959-4-anyNl7NRUj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88959-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88959-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: 2019-01/txt/msg02883.txt.bz2
Content-length: 319

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

--- Comment #1 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
I have found that this extra xor is not added when compiling with -O3
-march=sandybridge or -O3 -march=ivydybridge. However with -O3
-march=sandybridge/ivydybridge -mbmi it is added.
>From gcc-bugs-return-630075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:52:40 2019
Return-Path: <gcc-bugs-return-630075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 607 invoked by alias); 21 Jan 2019 18:52:39 -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 502 invoked by uid 48); 21 Jan 2019 18:52:34 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88847] gcc.target/aarch64/sve/struct_move_1.c ICE with -fstack-protector-strong
Date: Mon, 21 Jan 2019 18:52: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: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris 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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88847-4-V9flMY8p5X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88847-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: 2019-01/txt/msg02884.txt.bz2
Content-length: 479

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

--- Comment #3 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
right, so it seems this is an SVE issue and doesn't have much to do with stack
protector.

The issue is that aarch64_sve_struct_memory_operand_p doesn't take into account
whether it is before or after reload.  Before reload we need to allow any
offset since reload would do what it does and either split it or make the
address legitimate in some way.
>From gcc-bugs-return-630076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:53:14 2019
Return-Path: <gcc-bugs-return-630076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1682 invoked by alias); 21 Jan 2019 18:53:14 -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 1588 invoked by uid 48); 21 Jan 2019 18:53:10 -0000
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87038] diagnostics: Have -Wjump-misses-init be enabled by -Wall or -Wextra
Date: Mon, 21 Jan 2019 18:53: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: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: harald at gigawatt dot nl
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:
Message-ID: <bug-87038-4-SpzBcV7WMP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87038-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87038-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: 2019-01/txt/msg02885.txt.bz2
Content-length: 816

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

--- Comment #23 from Harald van Dijk <harald at gigawatt dot nl> ---
(In reply to Eric Gallager from comment #22)
> (In reply to Harald van Dijk from comment #21)
> > Since -Wjump-misses-init triggers too often for commonly used C patterns,
> > I do not think it is appropriate to include it in -Wall. 
> 
> OK, so what about -Wextra then?

My personal feeling as a user is that clang's warning is useful enough that if
GCC were to implement that, that one could be included in -Wall. It avoids
warning for the common cases where code works as intended, and still manages to
warn for the OP's code. I do not know how much work it would be to implement
that; if it would be too much work, then including -Wjump-misses-init in
-Wextra makes sense to me.
>From gcc-bugs-return-630077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 18:54:04 2019
Return-Path: <gcc-bugs-return-630077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3044 invoked by alias); 21 Jan 2019 18:54: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 2910 invoked by uid 48); 21 Jan 2019 18:53:58 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 18:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-Leic3RO2jc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02886.txt.bz2
Content-length: 2052

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

--- Comment #17 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #14)
>   I've checked cvtf_1.c generated code and I don't see additional fmov
> anymore.  I guess it was fixed by an ira-costs.c change (a special
> consideration of moves containing hard regs).  I think this PR is resolved
> (although the change resulted in a new PR 88560 but it is a different story).

Some failures disappeared, however various failures still exist. It appears the
ones reported above are not all directly related to the move change, but
another change around the same time. For example all of these are due to
combine no longer creating bfi or tst instructions in trivial cases:

FAIL: gcc.target/aarch64/combine_bfi_1.c scan-assembler-times \\tbfi\\t 5
FAIL: gcc.target/aarch64/insv_1.c scan-assembler bfi\tx[0-9]+, x[0-9]+, 0, 8
FAIL: gcc.target/aarch64/insv_1.c scan-assembler bfi\tx[0-9]+, x[0-9]+, 16, 5
FAIL: gcc.target/aarch64/insv_1.c scan-assembler movk\tx[0-9]+, 0x1d6b, lsl 32
FAIL: gcc.target/aarch64/insv_2.c scan-assembler bfi\tx[0-9]+, x[0-9]+, 43, 5
FAIL: gcc.target/aarch64/insv_2.c scan-assembler bfi\tx[0-9]+, x[0-9]+, 56, 8
FAIL: gcc.target/aarch64/insv_2.c scan-assembler movk\tx[0-9]+, 0x1d6b, lsl 16
FAIL: gcc.target/aarch64/lsl_asr_sbfiz.c scan-assembler sbfiz\tw
FAIL: gcc.target/aarch64/tst_5.c scan-assembler tst\t(x|w)[0-9]+,[ \t]*255
FAIL: gcc.target/aarch64/tst_5.c scan-assembler tst\t(x|w)[0-9]+,[ \t]*65535
FAIL: gcc.target/aarch64/tst_6.c scan-assembler tst\t(x|w)[0-9]+,[ \t]*65535

>   If we want to improve the generated code size, it would be better to find
> a small testcase from SPEC2006 showing what is wrong.  I understand it is a
> hard work but otherwise we could only speculate what is going wrongly.  I
> don't think that reverting the combiner change would be a solution.

Yes it's hard to get good reproducible examples, especially from large
functions. It's easier to first sort out the known test failures.
>From gcc-bugs-return-630078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:01:52 2019
Return-Path: <gcc-bugs-return-630078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31491 invoked by alias); 21 Jan 2019 19:01:52 -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 25102 invoked by uid 48); 21 Jan 2019 19:01:48 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators
Date: Mon, 21 Jan 2019 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wojciech_mula at poczta dot onet.pl
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:
Message-ID: <bug-88916-4-Y7selvbeE5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88916-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: 2019-01/txt/msg02887.txt.bz2
Content-length: 285

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

--- Comment #2 from Wojciech Mula <wojciech_mula at poczta dot onet.pl> ---
(In reply to Richard Biener from comment #1)
> Confirmed.

The first case is OK, but the second (for `both_nonzero`) is obviously wrong.
Sorry for that.
>From gcc-bugs-return-630079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:11:02 2019
Return-Path: <gcc-bugs-return-630079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75731 invoked by alias); 21 Jan 2019 19:11:02 -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 75672 invoked by uid 48); 21 Jan 2019 19:10:57 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88955] transparent_union for vector types not accepted
Date: Mon, 21 Jan 2019 19:11: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88955-4-80RH6TMH80@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88955-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: 2019-01/txt/msg02888.txt.bz2
Content-length: 476

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

--- Comment #1 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #0)
> Adding a dummy __int128 field makes GCC accept the code (but such workaround
> won't work for wider vectors, or on 32-bit).

But this causes the union to be passed in a pair of general 64-bit registers
(as expected for __int128) rather than in an SSE register. So that's not a
suitable workaround.
>From gcc-bugs-return-630080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:17:27 2019
Return-Path: <gcc-bugs-return-630080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91821 invoked by alias); 21 Jan 2019 19:17:27 -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 86674 invoked by uid 48); 21 Jan 2019 19:17:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88949] ICE in expand_expr_real_1, at expr.c:10001 with -fopenmp
Date: Mon, 21 Jan 2019 19:17: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: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-88949-4-s34eZE048L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88949-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: 2019-01/txt/msg02889.txt.bz2
Content-length: 689

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-21
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45484
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45484&action=edit
gcc9-pr88949.patch

Untested fix.
>From gcc-bugs-return-630081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:31:21 2019
Return-Path: <gcc-bugs-return-630081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45273 invoked by alias); 21 Jan 2019 19:31:17 -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 28654 invoked by uid 48); 21 Jan 2019 19:30:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Mon, 21 Jan 2019 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88953-4-9l8t9kbbcT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88953-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: 2019-01/txt/msg02890.txt.bz2
Content-length: 273

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can't reproduce with a cross-compiler, neither current 8.2.1 with -O3
-march=zEC12 nor -O3 -march=z14, nor with current trunk and the same options.
>From gcc-bugs-return-630082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:41:43 2019
Return-Path: <gcc-bugs-return-630082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87150 invoked by alias); 21 Jan 2019 19:41:43 -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 87013 invoked by uid 48); 21 Jan 2019 19:41:39 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86205] [9 Regression] ICE on valid C++11 code: in type_dependent_expression_p, at cp/pt.c:25193
Date: Mon, 21 Jan 2019 19:41: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86205-4-a6hkPGI4v2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86205-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86205-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: 2019-01/txt/msg02891.txt.bz2
Content-length: 423

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:44:35 2019
Return-Path: <gcc-bugs-return-630083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91058 invoked by alias); 21 Jan 2019 19:44:35 -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 90742 invoked by uid 48); 21 Jan 2019 19:44:30 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88959] Unnecessary xor before bsf/tzcnt
Date: Mon, 21 Jan 2019 19:44: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.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail 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: bug_status resolution
Message-ID: <bug-88959-4-2SS7hsnMEi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88959-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88959-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: 2019-01/txt/msg02892.txt.bz2
Content-length: 686

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
This is by design, see x86-tune.def:

/* X86_TUNE_AVOID_FALSE_DEP_FOR_BMI: Avoid false dependency
   for bit-manipulation instructions.  */
DEF_TUNE (X86_TUNE_AVOID_FALSE_DEP_FOR_BMI, "avoid_false_dep_for_bmi",
          m_SANDYBRIDGE | m_CORE_AVX2 | m_GENERIC)
>From gcc-bugs-return-630084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:46:13 2019
Return-Path: <gcc-bugs-return-630084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92836 invoked by alias); 21 Jan 2019 19:45:52 -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 92537 invoked by uid 48); 21 Jan 2019 19:45:26 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88294] [9 Regression] ICE on (invalid) C++11 code: in tsubst_copy, at cp/pt.c:15391
Date: Mon, 21 Jan 2019 19:45: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88294-4-A0nQe7pFEX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88294-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: 2019-01/txt/msg02893.txt.bz2
Content-length: 519

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
           Assignee|jason at gcc dot gnu.org           |unassigned at gcc dot gnu.org

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Marek, this seems related to your recent patch for 86476, want to take it?
>From gcc-bugs-return-630085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:46:57 2019
Return-Path: <gcc-bugs-return-630085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94314 invoked by alias); 21 Jan 2019 19:46:57 -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 94178 invoked by uid 48); 21 Jan 2019 19:46:48 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88293] [9 Regression] ICE on C++11 code: in build_target_expr_with_type, at cp/tree.c:793
Date: Mon, 21 Jan 2019 19:46: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88293-4-6mIHFnvMYg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88293-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88293-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: 2019-01/txt/msg02894.txt.bz2
Content-length: 452

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |jason at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jason at gcc dot gnu.org
>From gcc-bugs-return-630086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:49:47 2019
Return-Path: <gcc-bugs-return-630086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98018 invoked by alias); 21 Jan 2019 19:49: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 97887 invoked by uid 48); 21 Jan 2019 19:49:42 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 19:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-KEDrxPl4hG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02895.txt.bz2
Content-length: 175

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

--- Comment #18 from Segher Boessenkool <segher at gcc dot gnu.org> ---
https://gcc.gnu.org/ml/gcc/2019-01/msg00112.html
>From gcc-bugs-return-630087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:51:06 2019
Return-Path: <gcc-bugs-return-630087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126027 invoked by alias); 21 Jan 2019 19:51:05 -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 123743 invoked by uid 48); 21 Jan 2019 19:51:01 -0000
From: "weeks at iastate dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88960] New: [F18] ISO_FORTRAN_ENV: add INITIAL_TEAM, PARENT_TEAM, and CURRENT_TEAM
Date: Mon, 21 Jan 2019 19:51: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: weeks at iastate dot edu
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88960-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: 2019-01/txt/msg02896.txt.bz2
Content-length: 2714

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

            Bug ID: 88960
           Summary: [F18] ISO_FORTRAN_ENV: add INITIAL_TEAM, PARENT_TEAM,
                    and CURRENT_TEAM
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: weeks at iastate dot edu
  Target Milestone: ---

The Fortran 2018 standard (N2146 draft) defines the GET_TEAM() intrinsic
function as:

==============================================================================
16.9.85 GET_TEAM ([LEVEL])
...
3 Argument. LEVEL (optional) shall be a scalar integer whose value is equal to
one of the named constants INITIAL_TEAM, PARENT_TEAM, or CURRENT_TEAM from the
intrinsic module ISO_FORTRAN_ENV.
==============================================================================

gfortran 8.2.0 does not provide these constants in ISO_FORTRAN_ENV:
==============================================================================
$ cat test_level.f90
use, intrinsic ::  iso_fortran_env, only: INITIAL_TEAM, PARENT_TEAM,
CURRENT_TEAM
end
$ gfortran test_level.f90
test_level.f90:1:41:

 use, intrinsic ::  iso_fortran_env, only: INITIAL_TEAM, PARENT_TEAM,
CURRENT_TEAM
                                         1
Error: Symbol 'initial_team' referenced at (1) not found in intrinsic module
ISO_FORTRAN_ENV
test_level.f90:1:55:

 use, intrinsic ::  iso_fortran_env, only: INITIAL_TEAM, PARENT_TEAM,
CURRENT_TEAM
                                                       1
Error: Symbol 'parent_team' referenced at (1) not found in intrinsic module
ISO_FORTRAN_ENV
test_level.f90:1:68:

 use, intrinsic ::  iso_fortran_env, only: INITIAL_TEAM, PARENT_TEAM,
CURRENT_TEAM
                                                                    1
Error: Symbol 'current_team' referenced at (1) not found in intrinsic module
ISO_FORTRAN_ENV
==============================================================================
>From gcc-bugs-return-630089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:53:40 2019
Return-Path: <gcc-bugs-return-630089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20836 invoked by alias); 21 Jan 2019 19:53:40 -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 20713 invoked by uid 55); 21 Jan 2019 19:53:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88901] ICE when using -fsanitize=pointer-compare
Date: Mon, 21 Jan 2019 19:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88901-4-hJ7bmvqtTm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88901-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88901-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: 2019-01/txt/msg02898.txt.bz2
Content-length: 666

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 21 19:53:04 2019
New Revision: 268122

URL: https://gcc.gnu.org/viewcvs?rev=268122&root=gcc&view=rev
Log:
        PR sanitizer/88901
        * typeck.c (cp_build_binary_op): Don't instrument
        SANITIZE_POINTER_COMPARE if processing_template_decl.
        (pointer_diff): Similarly for SANITIZE_POINTER_SUBTRACT.

        * g++.dg/asan/pr88901.C: New test.

Added:
    trunk/gcc/testsuite/g++.dg/asan/pr88901.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/typeck.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:53:22 2019
Return-Path: <gcc-bugs-return-630088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19869 invoked by alias); 21 Jan 2019 19:53:22 -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 19805 invoked by uid 48); 21 Jan 2019 19:53:17 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88956] [9 Regression] ICE: Floating point exception
Date: Mon, 21 Jan 2019 19:53: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-88956-4-oTO9QBaywI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88956-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: 2019-01/txt/msg02897.txt.bz2
Content-length: 557

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-21
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1

--- Comment #1 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Confirmed on x86_64-linux-gnu.
>From gcc-bugs-return-630090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:54:56 2019
Return-Path: <gcc-bugs-return-630090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24342 invoked by alias); 21 Jan 2019 19:54:56 -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 24274 invoked by uid 48); 21 Jan 2019 19:54:51 -0000
From: "weeks at iastate dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88960] [F18] ISO_FORTRAN_ENV: add INITIAL_TEAM, PARENT_TEAM, and CURRENT_TEAM
Date: Mon, 21 Jan 2019 19:54: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: weeks at iastate dot edu
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88960-4-FMSwjQwMzy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88960-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: 2019-01/txt/msg02899.txt.bz2
Content-length: 189

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

--- Comment #1 from Nathan Weeks <weeks at iastate dot edu> ---
Note that GET_TEAM() itself is currently broken in gfortran (pr88154).
>From gcc-bugs-return-630091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 19:58:24 2019
Return-Path: <gcc-bugs-return-630091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50304 invoked by alias); 21 Jan 2019 19:58:22 -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 50194 invoked by uid 48); 21 Jan 2019 19:58:17 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35276] Doc should described how to compile mixed-language programs
Date: Mon, 21 Jan 2019 19: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: 4.4.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
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-35276-4-JpViVoJsdb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35276-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: 2019-01/txt/msg02900.txt.bz2
Content-length: 481

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #4 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
It seems that at least Thomas and Dominique believe that this can be closed.
>From gcc-bugs-return-630092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:01:31 2019
Return-Path: <gcc-bugs-return-630092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99516 invoked by alias); 21 Jan 2019 20:01: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 99267 invoked by uid 48); 21 Jan 2019 20:00:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88901] ICE when using -fsanitize=pointer-compare
Date: Mon, 21 Jan 2019 20:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88901-4-ijywxHwhVL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88901-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88901-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: 2019-01/txt/msg02901.txt.bz2
Content-length: 146

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-630093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:16:51 2019
Return-Path: <gcc-bugs-return-630093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2877 invoked by alias); 21 Jan 2019 20:16:51 -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 123484 invoked by uid 55); 21 Jan 2019 20:16:03 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] ICE in extract_insn, at recog.c:2304
Date: Mon, 21 Jan 2019 20:16: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uros at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88938-4-q3UPTms6MY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88938-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: 2019-01/txt/msg02902.txt.bz2
Content-length: 657

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

--- Comment #3 from uros at gcc dot gnu.org ---
Author: uros
Date: Mon Jan 21 20:14:40 2019
New Revision: 268123

URL: https://gcc.gnu.org/viewcvs?rev=268123&root=gcc&view=rev
Log:
        PR target/88938
        * config/i386/i386.c (ix86_expand_builtin) [case IX86_BUILTIN_BEXTRI32,
        case IX86_BUILTIN_BEXTRI64]: Sanitize operands.

testsuite/ChangeLog:

        PR target/88938
        * gcc.target/i386/pr88938.c: New test.


Added:
    trunk/gcc/testsuite/gcc.target/i386/pr88938.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:16:53 2019
Return-Path: <gcc-bugs-return-630094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3389 invoked by alias); 21 Jan 2019 20:16:53 -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 123677 invoked by uid 48); 21 Jan 2019 20:16:25 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88850] [9 Regression] Hard register coming out of expand causing reload to fail.
Date: Mon, 21 Jan 2019 20:16: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88850-4-P9LzMeFPYh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88850-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: 2019-01/txt/msg02903.txt.bz2
Content-length: 1360

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

--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Tamar Christina from comment #5)
> So yeah it seems that there are three issues here:
> 
> 1) We should probably have an r -> r alternative for *neon_mov.
> 2) The costs are now flipped from what they were before, for some reason the
> VFP regs are now way more expensive.
> 3) reload shouldn't have ICEd since it says
> 
> r113: preferred GENERAL_REGS, alternative ALL_REGS, allocno ALL_REGS
> 
> so it hasn't excluded ALL_REGS as an alternative, which should have either
> a) used the VPF register again or
> b) spilled the register since we have a m -> r and r -> m pattern.

p113 is used in 2 move insns, both containing 2 general hard regs (r0 and r2). 
So it is natural to use general regs for p113.  At least arm_register_move_cost
says this.

LRA does not check constraints because arm_register_move_cost for general regs
in any mode returns 2.  Such LRA/reload behaviour for cost 2 is described in
gcc documentation.

So adding r,r alternative to neon_movv8qi or increasing move cost for
GENERAL_REGS or both will solve the problem.

Actually the cost should be increased in anyway. It can not be 2 because we
need 2 general hard regs for V8QImode.  And this is a work for arm target
maintainers.
>From gcc-bugs-return-630095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:23:26 2019
Return-Path: <gcc-bugs-return-630095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31821 invoked by alias); 21 Jan 2019 20:23:26 -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 31713 invoked by uid 48); 21 Jan 2019 20:23:22 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Mon, 21 Jan 2019 20:23: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-87935-4-Zpm2Y5OMRU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg02904.txt.bz2
Content-length: 453

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |aoliva at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jason at gcc dot gnu.org
>From gcc-bugs-return-630096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:25:25 2019
Return-Path: <gcc-bugs-return-630096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34155 invoked by alias); 21 Jan 2019 20:25: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 33401 invoked by uid 48); 21 Jan 2019 20:24:25 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87893] [9 Regression] ICE in gimplify_expr, at gimplify.c:12557 on arm-linux-gnueabi
Date: Mon, 21 Jan 2019 20:25: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-87893-4-mtlbTwgvQe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87893-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: 2019-01/txt/msg02905.txt.bz2
Content-length: 378

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jason at gcc dot gnu.org
>From gcc-bugs-return-630097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:35:59 2019
Return-Path: <gcc-bugs-return-630097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63018 invoked by alias); 21 Jan 2019 20:35:59 -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 62924 invoked by uid 48); 21 Jan 2019 20:35:53 -0000
From: "konraddabrowski at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87770] [8/9 Regression] ICE in type_dependent_expression_p, at cp/pt.c:25230
Date: Mon, 21 Jan 2019 20:35: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: konraddabrowski at yahoo dot co.uk
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87770-4-kYKS6YMRhW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87770-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: 2019-01/txt/msg02906.txt.bz2
Content-length: 461

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

--- Comment #5 from Konrad Dabrowski <konraddabrowski at yahoo dot co.uk> ---
(In reply to Alexandre Oliva from comment #4)
> Created attachment 45448 [details]
> Candidate patch

I don't know enough about gcc to assess whether this is the "correct" solution,
but I can confirm that this patch prevents the ICE both in trunk and in the
gcc-8 branch. (It also fixes the ICE in the duplicate bug #87714.)
>From gcc-bugs-return-630098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:40:01 2019
Return-Path: <gcc-bugs-return-630098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67803 invoked by alias); 21 Jan 2019 20:40:01 -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 67611 invoked by uid 48); 21 Jan 2019 20:39:57 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Mon, 21 Jan 2019 20:40: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88787-4-s6L46zrDfb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-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: 2019-01/txt/msg02907.txt.bz2
Content-length: 378

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jason at gcc dot gnu.org
>From gcc-bugs-return-630099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:41:18 2019
Return-Path: <gcc-bugs-return-630099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69753 invoked by alias); 21 Jan 2019 20:41:17 -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 69569 invoked by uid 48); 21 Jan 2019 20:41:13 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88616] [9 Regression] ICE in gimplify_expr at gcc/gimplify.c:13363
Date: Mon, 21 Jan 2019 20:41: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88616-4-HrWZP0Xil8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88616-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: 2019-01/txt/msg02908.txt.bz2
Content-length: 486

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> ---
.

*** This bug has been marked as a duplicate of bug 87935 ***
>From gcc-bugs-return-630100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:41:19 2019
Return-Path: <gcc-bugs-return-630100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69908 invoked by alias); 21 Jan 2019 20:41:18 -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 69646 invoked by uid 48); 21 Jan 2019 20:41:14 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Mon, 21 Jan 2019 20:41: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87935-4-fFSiMDTKQ1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg02909.txt.bz2
Content-length: 440

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 88616 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-630101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:42:05 2019
Return-Path: <gcc-bugs-return-630101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73275 invoked by alias); 21 Jan 2019 20:42: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 73084 invoked by uid 48); 21 Jan 2019 20:42:00 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87893] [9 Regression] ICE in gimplify_expr, at gimplify.c:12557 on arm-linux-gnueabi
Date: Mon, 21 Jan 2019 20:42: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87893-4-SkEjJ9GV0y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87893-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: 2019-01/txt/msg02910.txt.bz2
Content-length: 486

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
.

*** This bug has been marked as a duplicate of bug 87935 ***
>From gcc-bugs-return-630102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:42:07 2019
Return-Path: <gcc-bugs-return-630102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73520 invoked by alias); 21 Jan 2019 20:42:07 -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 73177 invoked by uid 48); 21 Jan 2019 20:42:02 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Mon, 21 Jan 2019 20:42: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87935-4-7QgCXTrRkK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg02911.txt.bz2
Content-length: 181

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

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 87893 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-630103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:43:09 2019
Return-Path: <gcc-bugs-return-630103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75738 invoked by alias); 21 Jan 2019 20:43:09 -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 75477 invoked by uid 48); 21 Jan 2019 20:43:04 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Mon, 21 Jan 2019 20:43: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88787-4-5gYB6JuIa5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-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: 2019-01/txt/msg02912.txt.bz2
Content-length: 486

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
.

*** This bug has been marked as a duplicate of bug 87935 ***
>From gcc-bugs-return-630104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:43:14 2019
Return-Path: <gcc-bugs-return-630104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76226 invoked by alias); 21 Jan 2019 20:43:13 -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 75648 invoked by uid 48); 21 Jan 2019 20:43:08 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Mon, 21 Jan 2019 20:43: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87935-4-1csP74XbEN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg02913.txt.bz2
Content-length: 442

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tnfchris at gcc dot gnu.org

--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 88787 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-630105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:44:36 2019
Return-Path: <gcc-bugs-return-630105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78513 invoked by alias); 21 Jan 2019 20:44:36 -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 78395 invoked by uid 48); 21 Jan 2019 20:44:31 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Mon, 21 Jan 2019 20:44: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-AQPToXZGPf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02914.txt.bz2
Content-length: 2581

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

--- Comment #16 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #13)
> So, both the following patches should fix it IMHO, but no idea which one if
> any is right.
> With
> --- gcc/config/rs6000/vsx.md.jj	2019-01-01 12:37:44.305529527 +0100
> +++ gcc/config/rs6000/vsx.md	2019-01-18 18:07:37.194899062 +0100
> @@ -4356,7 +4356,9 @@
>    ""
>    [(const_int 0)]
>  {
> -  rtx hi = gen_highpart (DFmode, operands[1]);
> +  rtx hi = (BYTES_BIG_ENDIAN
> +	    ? gen_highpart (DFmode, operands[1])
> +	    : gen_lowpart (DFmode, operands[1]));
>    rtx lo = (GET_CODE (operands[2]) == SCRATCH)
>  	    ? gen_reg_rtx (DFmode)
>  	    : operands[2];
> 
> the assembly changes:
> --- reduction-3.s1	2019-01-18 18:05:14.313229730 +0100
> +++ reduction-3.s2	2019-01-18 18:10:20.617233358 +0100
> @@ -27,7 +27,7 @@ MAIN__._omp_fn.0:
>  	addi 9,9,16
>  	bdnz .L2
>  	 # vec_extract to same register
> -	lfd 12,-8(1)
> +	lfd 12,-16(1)
>  	xsmaxdp 0,12,0
>  	stfd 0,0(10)
>  	blr
> with:
> --- gcc/config/rs6000/vsx.md.jj	2019-01-01 12:37:44.305529527 +0100
> +++ gcc/config/rs6000/vsx.md	2019-01-18 18:16:30.680186709 +0100
> @@ -4361,7 +4361,9 @@
>  	    ? gen_reg_rtx (DFmode)
>  	    : operands[2];
>  
> -  emit_insn (gen_vsx_extract_v2df (lo, operands[1], const1_rtx));
> +  emit_insn (gen_vsx_extract_v2df (lo, operands[1],
> +				   BYTES_BIG_ENDIAN
> +				   ? const1_rtx : const0_rtx));
>    emit_insn (gen_<VEC_reduc_rtx>df3 (operands[0], hi, lo));
>    DONE;
>  }

This is what looks right to me.  This code all pre-dates little-endian support,
and I think we missed changing the element to be extracted in this spot.  There
is probably something wrong with _v4sf_scalar also -- the gen_vsx_xxsldwi_v4sf
probably needs to be adjusted also for little-endian, but I have a hard time
following this code and I'm not certain.

Bill

> the assembly changes:
> --- reduction-3.s1	2019-01-18 18:05:14.313229730 +0100
> +++ reduction-3.s3	2019-01-18 18:17:18.977397458 +0100
> @@ -26,7 +26,7 @@ MAIN__._omp_fn.0:
>  	xxpermdi 0,0,0,2
>  	addi 9,9,16
>  	bdnz .L2
> -	 # vec_extract to same register
> +	xxpermdi 0,0,0,3
>  	lfd 12,-8(1)
>  	xsmaxdp 0,12,0
>  	stfd 0,0(10)
> 
> So just judging from this exact testcase, the first patch seems to be more
> efficient, though still unsure about that, because it goes through memory in
> either case, wouldn't it be better to emit a xxpermdi from 0 to 12 that
> swaps the two elements instead of loading it from memory?
>From gcc-bugs-return-630106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:50:10 2019
Return-Path: <gcc-bugs-return-630106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125124 invoked by alias); 21 Jan 2019 20:50: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 124967 invoked by uid 48); 21 Jan 2019 20:50:04 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86943] [7/8/9 Regression] Wrong code when converting stateless generic lambda to function pointer
Date: Mon, 21 Jan 2019 20:50: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-86943-4-LAk42hhxqM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86943-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86943-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: 2019-01/txt/msg02915.txt.bz2
Content-length: 378

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jason at gcc dot gnu.org
>From gcc-bugs-return-630107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:51:22 2019
Return-Path: <gcc-bugs-return-630107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127851 invoked by alias); 21 Jan 2019 20:51: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 127726 invoked by uid 48); 21 Jan 2019 20:51:16 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Mon, 21 Jan 2019 20:51: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-1CFii2tnvP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02916.txt.bz2
Content-length: 514

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

--- Comment #17 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Actually I *think* the *vsx_reduc_<VEC_reduc_name>_v4sf_scalar code is probably
okay.  This is all being done with insns that should leave the reduction result
in the right-hand element of the register (element 3 for BE, as is referenced
in the xxsldwi insn).

I'll regtest a patch with Jakub's second alternative from above, which matches
my understanding of the current flaw.

Bill
>From gcc-bugs-return-630108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 20:59:10 2019
Return-Path: <gcc-bugs-return-630108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56498 invoked by alias); 21 Jan 2019 20:59: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 56460 invoked by uid 48); 21 Jan 2019 20:59:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Mon, 21 Jan 2019 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_status everconfirmed
Message-ID: <bug-88950-4-p2HAsbzShA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88950-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: 2019-01/txt/msg02917.txt.bz2
Content-length: 351

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |UNCONFIRMED
     Ever confirmed|1                           |0
>From gcc-bugs-return-630109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:05:41 2019
Return-Path: <gcc-bugs-return-630109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63282 invoked by alias); 21 Jan 2019 21:05:41 -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 63164 invoked by uid 48); 21 Jan 2019 21:05:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Mon, 21 Jan 2019 21:05: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-p8MwUMc8Zp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02918.txt.bz2
Content-length: 934

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

--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The comment on the define_insn_and_split says:
;; Combiner patterns with the vector reduction patterns that knows we can get
;; to the top element of the V2DF array without doing an extract.
So, the question is, is that ever the case for little endian also?
As I said,
--- gcc/config/rs6000/vsx.md    2019-01-19 09:39:13.224924063 +0100
+++ gcc/config/rs6000/vsx.md    2019-01-21 22:04:15.372792335 +0100
@@ -4351,7 +4351,7 @@
          (match_dup 1))
         (parallel [(const_int 1)])))
    (clobber (match_scratch:DF 2 "=0,0,&wd,&wa"))]
-  "VECTOR_UNIT_VSX_P (V2DFmode)"
+  "BYTES_BIG_ENDIAN && VECTOR_UNIT_VSX_P (V2DFmode)"
   "#"
   ""
   [(const_int 0)]
generates much better code at least on this testcase, and from
bootstrap/regtest I'm not away of this pattern ever trigging for something
different.
>From gcc-bugs-return-630110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:11:47 2019
Return-Path: <gcc-bugs-return-630110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81201 invoked by alias); 21 Jan 2019 21:11:47 -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 81103 invoked by uid 48); 21 Jan 2019 21:11:43 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Mon, 21 Jan 2019 21:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-9CpTHXOS9p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02919.txt.bz2
Content-length: 642

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

--- Comment #19 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #18)
> https://gcc.gnu.org/ml/gcc/2019-01/msg00112.html

Thanks, I hadn't noticed that yet... I need to look at it in more detail, but
are you saying that combine no longer generates zero_extracts today and all
patterns that rely on it must be changed to a different canonical form?

I suspect the tst_5/6 cases are similar if the canonical form of rtl has
changed. Note that doing (x & 63) != 0 just works fine, it's only 255 and 65535
which appear to be treated differently...
>From gcc-bugs-return-630111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:30:41 2019
Return-Path: <gcc-bugs-return-630111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115051 invoked by alias); 21 Jan 2019 21:30:28 -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 114619 invoked by uid 48); 21 Jan 2019 21:30:05 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88961] New: valgrind error in resolve_ref
Date: Mon, 21 Jan 2019 21:30: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88961-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: 2019-01/txt/msg02920.txt.bz2
Content-length: 1457

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

            Bug ID: 88961
           Summary: valgrind error in resolve_ref
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For a valgrind version of recent gcc trunk and testsuite
file ./gfortran.dg/actual_array_substr_3.f90, I get

./gfortran.dg/actual_array_substr_3.f90
==5000== Invalid read of size 8
==5000==    at 0x68A150: resolve_ref(gfc_expr*) (resolve.c:5082)
==5000==    by 0x683DE3: resolve_variable (resolve.c:5536)
==5000==    by 0x683DE3: gfc_resolve_expr(gfc_expr*) (resolve.c:6852)
==5000==    by 0x68635D: resolve_actual_arglist(gfc_actual_arglist*,
procedure_type, bool) (resolve.c:1916)

$ ~/gcc/results/bin/gfortran -v
Using built-in specs.
COLLECT_GCC=/home/dcb/gcc/results/bin/gfortran
COLLECT_LTO_WRAPPER=/home/dcb/gcc/results.268000.valgrind/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../trunk/configure
--prefix=/home/dcb/gcc/results.268000.valgrind --disable-bootstrap
--disable-multilib --disable-werror --enable-checking=valgrind
--enable-languages=c,c++,fortran
Thread model: posix
gcc version 9.0.0 20190117 (experimental) (GCC) 
$
>From gcc-bugs-return-630112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:35:23 2019
Return-Path: <gcc-bugs-return-630112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119195 invoked by alias); 21 Jan 2019 21:35:22 -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 119042 invoked by uid 48); 21 Jan 2019 21:35:18 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Mon, 21 Jan 2019 21:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88936-4-rXfgH6rMrV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg02921.txt.bz2
Content-length: 509

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

--- Comment #8 from Sergei Trofimovich <slyfox at inbox dot ru> ---
(In reply to Martin LiÅ¡ka from comment #3)
> Confirmed, started with r231498.

That was really fast!

Minor comment: 'git tag' says that revision was added before gcc-6.1.0. 
Running test locally says 6.4.0 (and 6.5.0) is also broken. Last working
version was gcc-5.5.0.

Or I'm interpreting the field 'Known to work: 6.4.0' incorrectly and it's the
token past support horizon?
>From gcc-bugs-return-630113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:44:19 2019
Return-Path: <gcc-bugs-return-630113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2430 invoked by alias); 21 Jan 2019 21:44:18 -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 1482 invoked by uid 48); 21 Jan 2019 21:44:13 -0000
From: "jirik.svoboda at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88962] New: Invalid/inconsistent PowerPC TLS variable access
Date: Mon, 21 Jan 2019 21:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jirik.svoboda at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88962-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: 2019-01/txt/msg02922.txt.bz2
Content-length: 3776

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

            Bug ID: 88962
           Summary: Invalid/inconsistent PowerPC TLS variable access
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jirik.svoboda at seznam dot cz
  Target Milestone: ---

If I build a GCC cross-compiler for PowerPC (ppc-linux-gnu):
binutils-2.31.1
./configure --target=ppc-linux-gnu --prefix=... --dsiable-nls --disable-werror
--enable-gold --enable-deterministic-archives
make all
make install

gcc-8.2.0
./configure --target=ppc-linux-gnu --prefix=... --with-gnu-as --with-gnu-ld
--disable-nls --disable-threads --enable-languages=c --disable-multilib
--disable-libgcj --without-headers --disable-shared --enable-lto
--disable-werror
make all-gcc
make install-gcc

and then build a shared library that accesses a static thread-local variable
and a non-static thread-local variable:

[jirka@omelette tmp]$ cat test.c
static __thread int a;
__thread int b;

int geta(void)
{
        return a;
}

int getb(void)
{
        return b;
}

int seta(int n)
{
        a =  n;
}


[jirka@omelette tmp]$ /usr/local/xcross/ppc-linux-gnu/bin/ppc-linux-gnu-gcc
-nostdlib -fPIC -O3 -c -o test.o test.c
[jirka@omelette tmp]$ /usr/local/xcross/ppc-linux-gnu/bin/ppc-linux-gnu-gcc
-nostdlib -shared -fPIC -O3 -o test.so test.o

[jirka@omelette tmp]$ /usr/local/xcross/ppc-linux-gnu/bin/ppc-linux-gnu-objdump
-D test.so

00000248 <geta>:
 248:   7c 08 02 a6     mflr    r0
 24c:   42 9f 00 09     bcl     20,4*cr7+so,254 <geta+0xc>
 250:   00 01 fd c4     .long 0x1fdc4
 254:   7d 28 02 a6     mflr    r9
 258:   94 21 ff f0     stwu    r1,-16(r1)
 25c:   80 69 00 00     lwz     r3,0(r9)
 260:   90 01 00 14     stw     r0,20(r1)
 264:   7c 69 1a 14     add     r3,r9,r3
 268:   93 c1 00 08     stw     r30,8(r1)
 26c:   38 63 ff f4     addi    r3,r3,-12
 270:   48 01 fd f9     bl      20068 <__tls_get_addr@plt>
 274:   80 01 00 14     lwz     r0,20(r1)
 278:   3c 63 00 00     addis   r3,r3,0
 27c:   83 c1 00 08     lwz     r30,8(r1)
 280:   38 63 80 04     addi    r3,r3,-32764   <--- **** subtract bias 32K
 284:   7c 08 03 a6     mtlr    r0
 288:   80 63 00 00     lwz     r3,0(r3)
 28c:   38 21 00 10     addi    r1,r1,16
 290:   4e 80 00 20     blr


00000294 <getb>:
 294:   7c 08 02 a6     mflr    r0
 298:   42 9f 00 09     bcl     20,4*cr7+so,2a0 <getb+0xc>
 29c:   00 01 fd 78     .long 0x1fd78
 2a0:   7d 28 02 a6     mflr    r9
 2a4:   94 21 ff f0     stwu    r1,-16(r1)
 2a8:   80 69 00 00     lwz     r3,0(r9)
 2ac:   90 01 00 14     stw     r0,20(r1)
 2b0:   7c 69 1a 14     add     r3,r9,r3
 2b4:   93 c1 00 08     stw     r30,8(r1)
 2b8:   38 63 ff ec     addi    r3,r3,-20
 2bc:   48 01 fd ad     bl      20068 <__tls_get_addr@plt>
 2c0:   80 01 00 14     lwz     r0,20(r1)
 2c4:   80 63 00 00     lwz     r3,0(r3)    < ---- **** no bias subtracted
 2c8:   83 c1 00 08     lwz     r30,8(r1)
 2cc:   7c 08 03 a6     mtlr    r0
 2d0:   38 21 00 10     addi    r1,r1,16
 2d4:   4e 80 00 20     blr


As you can see, for static thread-local variable, we subtract 32K bias from
result of __tls_get_addr@plt. For non-static thread-local variable, we do not
subtract anything. This looks like a bug.

For -O0 optimization we never subtract anything.

Not sure which behavior is correct -- subtract 32 K or not) -- I ran into this
when implementing PowerPC architecture support for HelenOS dynamic linker. I am
inclined to think it should always subtract 32K bias according to the ABI. In
any case I think it needs to behave consistently, otherwise cannot make the TLS
work in all cases.
>From gcc-bugs-return-630114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:46:59 2019
Return-Path: <gcc-bugs-return-630114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5072 invoked by alias); 21 Jan 2019 21:46:58 -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 5002 invoked by uid 48); 21 Jan 2019 21:46:54 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Mon, 21 Jan 2019 21:46: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88954-4-BuFc3zBuEG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg02923.txt.bz2
Content-length: 879

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
I'm wondering if noplt is meant to be a property of the function pointer or
that of its type?

Either way, what should happen in cases when a noplt pointer is assigned the
address of a PLT function?  E.g.,:

  void (*p_noplt)(void) = f_noplt;

  void f (int i)
  {
    if (i < 0)
      p_noplt = f_plt;
  }

Do calls through p_noplt still happen without the use of the PLT after the
assignment?  Should a warning be issued when a noplt pointer is assigned the
address of an ordinary PLT function?
>From gcc-bugs-return-630115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 21:56:46 2019
Return-Path: <gcc-bugs-return-630115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50036 invoked by alias); 21 Jan 2019 21:56:45 -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 46749 invoked by uid 48); 21 Jan 2019 21:56:39 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88962] Invalid/inconsistent PowerPC TLS variable access
Date: Mon, 21 Jan 2019 21:56: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88962-4-nIkoaymRXH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88962-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88962-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: 2019-01/txt/msg02924.txt.bz2
Content-length: 278

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
What happens if you use -fno-section-anchors option?  My bet is the section
anchor is setting the bias for the static variables to be 32k off of the
center.
>From gcc-bugs-return-630116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:00:47 2019
Return-Path: <gcc-bugs-return-630116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122694 invoked by alias); 21 Jan 2019 22:00:47 -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 122636 invoked by uid 48); 21 Jan 2019 22:00:43 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Mon, 21 Jan 2019 22:00: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88954-4-bCu2rLoH4B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg02925.txt.bz2
Content-length: 772

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

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Martin Sebor from comment #1)
> I'm wondering if noplt is meant to be a property of the function pointer or
> that of its type?
> 
> Either way, what should happen in cases when a noplt pointer is assigned the
> address of a PLT function?  E.g.,:
> 
>   void (*p_noplt)(void) = f_noplt;
> 
>   void f (int i)
>   {
>     if (i < 0)
>       p_noplt = f_plt;
>   }
> 
> Do calls through p_noplt still happen without the use of the PLT after the
> assignment?  Should a warning be issued when a noplt pointer is assigned the
> address of an ordinary PLT function?

noplt attribute only applies to function, not function pointer.
>From gcc-bugs-return-630117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:04:49 2019
Return-Path: <gcc-bugs-return-630117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129355 invoked by alias); 21 Jan 2019 22:04:47 -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 129259 invoked by uid 48); 21 Jan 2019 22:04:43 -0000
From: "jirik.svoboda at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88962] Invalid/inconsistent PowerPC TLS variable access
Date: Mon, 21 Jan 2019 22:04: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jirik.svoboda at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88962-4-JjRnIAjh1s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88962-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88962-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: 2019-01/txt/msg02926.txt.bz2
Content-length: 245

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

--- Comment #2 from Jiri Svoboda <jirik.svoboda at seznam dot cz> ---
I added the -fno-section-anchors option to both the compile and link
invocations but I am still getting the same result.
>From gcc-bugs-return-630118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:07:59 2019
Return-Path: <gcc-bugs-return-630118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81524 invoked by alias); 21 Jan 2019 22:07:59 -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 81360 invoked by uid 48); 21 Jan 2019 22:07:55 -0000
From: "dinuxbg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88609] [avr] ice: insn does not satisfy its constraints while building libgcc
Date: Mon, 21 Jan 2019 22:07: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: 9.0
X-Bugzilla-Keywords: build, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinuxbg at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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_status resolution
Message-ID: <bug-88609-4-uN0GZqLofv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88609-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88609-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: 2019-01/txt/msg02927.txt.bz2
Content-length: 569

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

Dimitar Dimitrov <dinuxbg at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Dimitar Dimitrov <dinuxbg at gmail dot com> ---
Not an avr backend issue, but rather due to PR88753 bug in the host toolchain.

*** This bug has been marked as a duplicate of bug 88753 ***
>From gcc-bugs-return-630119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:08:00 2019
Return-Path: <gcc-bugs-return-630119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81897 invoked by alias); 21 Jan 2019 22:07:59 -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 81373 invoked by uid 48); 21 Jan 2019 22:07:55 -0000
From: "dinuxbg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] [9 Regression] Wrong code since r265463 in tree switch conversion
Date: Mon, 21 Jan 2019 22:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinuxbg at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88753-4-768Yi903pw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-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: 2019-01/txt/msg02928.txt.bz2
Content-length: 445

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

Dimitar Dimitrov <dinuxbg at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dinuxbg at gmail dot com

--- Comment #7 from Dimitar Dimitrov <dinuxbg at gmail dot com> ---
*** Bug 88609 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-630120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:13:47 2019
Return-Path: <gcc-bugs-return-630120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13984 invoked by alias); 21 Jan 2019 22:13:47 -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 13924 invoked by uid 48); 21 Jan 2019 22:13:43 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88560] [9 Regression] armv8_2-fp16-move-1.c and related regressions after r266385
Date: Mon, 21 Jan 2019 22:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88560-4-YEtRaHoqJZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88560-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: 2019-01/txt/msg02929.txt.bz2
Content-length: 240

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

--- Comment #8 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Created attachment 45485
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45485&action=edit
Proposed patch
>From gcc-bugs-return-630121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:14:35 2019
Return-Path: <gcc-bugs-return-630121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15214 invoked by alias); 21 Jan 2019 22:14:34 -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 15140 invoked by uid 48); 21 Jan 2019 22:14:31 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88560] [9 Regression] armv8_2-fp16-move-1.c and related regressions after r266385
Date: Mon, 21 Jan 2019 22:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88560-4-1vszXJkjsM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88560-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: 2019-01/txt/msg02930.txt.bz2
Content-length: 263

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

--- Comment #9 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #8)
> Created attachment 45485 [details]
> Proposed patch

Does this patch solves the problem?
>From gcc-bugs-return-630122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:34:29 2019
Return-Path: <gcc-bugs-return-630122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50939 invoked by alias); 21 Jan 2019 22:34:28 -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 50259 invoked by uid 55); 21 Jan 2019 22:34:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88949] ICE in expand_expr_real_1, at expr.c:10001 with -fopenmp
Date: Mon, 21 Jan 2019 22:34: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: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88949-4-G9e3jmzb5B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88949-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: 2019-01/txt/msg02931.txt.bz2
Content-length: 590

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 21 22:33:52 2019
New Revision: 268127

URL: https://gcc.gnu.org/viewcvs?rev=268127&root=gcc&view=rev
Log:
        PR c++/88949
        * optimize.c (cxx_copy_decl): New function.
        (clone_body): Use it instead of copy_decl_no_change.

        * g++.dg/gomp/pr88949.C: New test.

Added:
    trunk/gcc/testsuite/g++.dg/gomp/pr88949.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/optimize.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:36:13 2019
Return-Path: <gcc-bugs-return-630123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58724 invoked by alias); 21 Jan 2019 22:36:13 -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 58675 invoked by uid 48); 21 Jan 2019 22:36:09 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87996] [8/9 Regression] "size of array is negative" error when SIZE_MAX/2 < sizeof(array) <= SIZE_MAX
Date: Mon, 21 Jan 2019 22:36: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-87996-4-BUr7lrLRrr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87996-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: 2019-01/txt/msg02932.txt.bz2
Content-length: 466

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |msebor at gcc dot gnu.org

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Let me work on this.
>From gcc-bugs-return-630124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 22:40:07 2019
Return-Path: <gcc-bugs-return-630124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68223 invoked by alias); 21 Jan 2019 22:40:06 -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 68157 invoked by uid 48); 21 Jan 2019 22:40:02 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88821] Inline packing of non-contiguous arguments
Date: Mon, 21 Jan 2019 22:40: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88821-4-waQHfEcZLe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88821-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: 2019-01/txt/msg02933.txt.bz2
Content-length: 387

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

--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Created attachment 45486
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45486&action=edit
patch that appears to work

Plus a few additional test cases (it is necessary to split a few,
because internal_pack is no longer called with -O0 with this approach).
>From gcc-bugs-return-630125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 21 23:23:21 2019
Return-Path: <gcc-bugs-return-630125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1092 invoked by alias); 21 Jan 2019 23:23: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 1053 invoked by uid 48); 21 Jan 2019 23:23:16 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88963] New: gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Mon, 21 Jan 2019 23:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88963-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: 2019-01/txt/msg02934.txt.bz2
Content-length: 2592

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

            Bug ID: 88963
           Summary: gcc generates terrible code for vectors of 64+ length
                    which are not natively supported
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bugzilla@poradnik-webmastera.com
  Target Milestone: ---

[code]
typedef int VInt __attribute__((vector_size(64)));

void test(VInt*__restrict a, VInt*__restrict b, 
    VInt*__restrict c)
{
    *a = *b + *c;
}
[/code]

This code compiled with -O3 -march=skylake in following way:

[asm]
test(int __vector(16)*, int __vector(16)*, int __vector(16)*):
  push rbp
  mov rbp, rsp
  and rsp, -64
  sub rsp, 136
  vmovdqa xmm3, XMMWORD PTR [rsi]
  vmovdqa xmm4, XMMWORD PTR [rsi+16]
  vmovdqa xmm5, XMMWORD PTR [rsi+32]
  vmovdqa xmm6, XMMWORD PTR [rsi+48]
  vmovdqa xmm7, XMMWORD PTR [rdx]
  vmovaps XMMWORD PTR [rsp-56], xmm3
  vmovdqa xmm1, XMMWORD PTR [rdx+16]
  vmovaps XMMWORD PTR [rsp-40], xmm4
  vmovdqa ymm4, YMMWORD PTR [rsp-56]
  vmovdqa xmm2, XMMWORD PTR [rdx+32]
  vmovaps XMMWORD PTR [rsp-8], xmm6
  vmovaps XMMWORD PTR [rsp+8], xmm7
  vmovdqa xmm3, XMMWORD PTR [rdx+48]
  vmovaps XMMWORD PTR [rsp-24], xmm5
  vmovaps XMMWORD PTR [rsp+24], xmm1
  vpaddd ymm0, ymm4, YMMWORD PTR [rsp+8]
  vmovdqa ymm5, YMMWORD PTR [rsp-24]
  vmovaps XMMWORD PTR [rsp+40], xmm2
  vmovaps XMMWORD PTR [rsp+56], xmm3
  vmovdqa xmm2, xmm0
  vmovdqa YMMWORD PTR [rsp-120], ymm0
  vpaddd ymm0, ymm5, YMMWORD PTR [rsp+40]
  vmovdqa xmm6, XMMWORD PTR [rsp-104]
  vmovdqa YMMWORD PTR [rsp-88], ymm0
  vmovdqa xmm7, XMMWORD PTR [rsp-72]
  vmovaps XMMWORD PTR [rdi], xmm2
  vmovaps XMMWORD PTR [rdi+16], xmm6
  vmovaps XMMWORD PTR [rdi+32], xmm0
  vmovaps XMMWORD PTR [rdi+48], xmm7
  vzeroupper
  leave
  ret
[/asm]

Other compilers (clang, icc) produces nice code. This is from clang:

[asm]
test(int __vector(16)*, int __vector(16)*, int __vector(16)*): # @test(int
__vector(16)*, int __vector(16)*, int __vector(16)*)
  vmovdqa ymm0, ymmword ptr [rdx]
  vmovdqa ymm1, ymmword ptr [rdx + 32]
  vpaddd ymm0, ymm0, ymmword ptr [rsi]
  vpaddd ymm1, ymm1, ymmword ptr [rsi + 32]
  vmovdqa ymmword ptr [rdi + 32], ymm1
  vmovdqa ymmword ptr [rdi], ymm0
  vzeroupper
  ret
[/asm]

gcc produces pretty code for -O3 -march=skylake-avx512. Pretty code is also for
vector size 32 with AVX disabled. However for vector size 128 and -O3
-march=skylake-avx512 code is again ugly.
>From gcc-bugs-return-630126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 00:02:24 2019
Return-Path: <gcc-bugs-return-630126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88251 invoked by alias); 22 Jan 2019 00:02:23 -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 88161 invoked by uid 55); 22 Jan 2019 00:02:19 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38182] stddef.h assumes machinee/ansi.h defines _ANSI_H_
Date: Tue, 22 Jan 2019 00:02: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: 4.4.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-38182-4-Ggh1o5IHgc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38182-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38182-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: 2019-01/txt/msg02935.txt.bz2
Content-length: 250

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

--- Comment #20 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
r261797 removed all references to _ANSI_H_ from stddef.h, so this issue 
can't be relevant after then.
>From gcc-bugs-return-630127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 00:07:26 2019
Return-Path: <gcc-bugs-return-630127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100663 invoked by alias); 22 Jan 2019 00:07:25 -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 100514 invoked by uid 55); 22 Jan 2019 00:07:21 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Tue, 22 Jan 2019 00:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88927-4-MmdTdKYEeJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02936.txt.bz2
Content-length: 849

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

--- Comment #5 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Tue Jan 22 00:06:44 2019
New Revision: 268131

URL: https://gcc.gnu.org/viewcvs?rev=268131&root=gcc&view=rev
Log:
        PR go/88927
    runtime, internal/cpu: fix build for ARM GNU/Linux

    Was failing with

    ../../../libgo/go/internal/cpu/cpu.go:138:2: error: reference to undefined
name 'doinit'
      138 |  doinit()
          |  ^

    Fix it by adding in Go 1.12 internal/cpu/cpu_arm.go, and the code in
    runtime that initializes the values.

    Fixes https://gcc.gnu.org/PR88927.

    Reviewed-on: https://go-review.googlesource.com/c/158717

Added:
    trunk/libgo/go/internal/cpu/cpu_arm.go
Modified:
    trunk/gcc/go/gofrontend/MERGE
    trunk/libgo/go/runtime/os_linux_arm.go
>From gcc-bugs-return-630128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 00:09:13 2019
Return-Path: <gcc-bugs-return-630128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102663 invoked by alias); 22 Jan 2019 00:09:13 -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 102590 invoked by uid 48); 22 Jan 2019 00:09:09 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Tue, 22 Jan 2019 00:09: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-gKfvs3SOt9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg02937.txt.bz2
Content-length: 619

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

--- Comment #19 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The pattern makes no sense at all for LE.

If LE,

         (vec_concat:V2DF
          (vec_select:DF
           (match_operand:V2DF 1 "vfloat_operand" "wd,wa,wd,wa")
           (parallel [(const_int 1)]))
          (vec_select:DF
           (match_dup 1)
           (parallel [(const_int 0)])))

means exactly the same as just

         (match_operand:V2DF 1 "vfloat_operand" "wd,wa,wd,wa")


So how does this pattern ever match for LE anyway?  Are there some
serious missed simplifications?
>From gcc-bugs-return-630129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 00:10:57 2019
Return-Path: <gcc-bugs-return-630129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106088 invoked by alias); 22 Jan 2019 00:10:56 -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 106006 invoked by uid 48); 22 Jan 2019 00:10:53 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88927] [9 Regression] Bootstrap failure on arm in libgo starting with r268084
Date: Tue, 22 Jan 2019 00:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88927-4-1Sv7pcZd2H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88927-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: 2019-01/txt/msg02938.txt.bz2
Content-length: 483

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

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Ian Lance Taylor <ian at airs dot com> ---
The build problem is fixed, leaving the test failures for another day.
>From gcc-bugs-return-630130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 00:27:46 2019
Return-Path: <gcc-bugs-return-630130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100831 invoked by alias); 22 Jan 2019 00:27: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 100728 invoked by uid 48); 22 Jan 2019 00:27:41 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Tue, 22 Jan 2019 00:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-WODQbGx20M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg02939.txt.bz2
Content-length: 999

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

--- Comment #20 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Wilco from comment #19)
> (In reply to Segher Boessenkool from comment #18)
> > https://gcc.gnu.org/ml/gcc/2019-01/msg00112.html
> 
> Thanks, I hadn't noticed that yet... I need to look at it in more detail,
> but are you saying that combine no longer generates zero_extracts today and
> all patterns that rely on it must be changed to a different canonical form?

If you no longer see zero_extracts there must be some other reason for it.

> I suspect the tst_5/6 cases are similar if the canonical form of rtl has
> changed.

It hasn't.

> Note that doing (x & 63) != 0 just works fine, it's only 255 and
> 65535 which appear to be treated differently...

Yes, those are "simplified" to some subreg or whatever.  This isn't new.
It's what change_zero_ext is for, so that you don't have to deal with those
forms if you have more generic instructions.
>From gcc-bugs-return-630131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 00:40:23 2019
Return-Path: <gcc-bugs-return-630131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59360 invoked by alias); 22 Jan 2019 00:40:23 -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 59246 invoked by uid 48); 22 Jan 2019 00:40:18 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35276] Doc should described how to compile mixed-language programs
Date: Tue, 22 Jan 2019 00:40: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.4.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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-35276-4-rsMMZDnqN9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35276-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: 2019-01/txt/msg02940.txt.bz2
Content-length: 541

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

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |egallager at gcc dot gnu.org

--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to JÃ¼rgen Reuter from comment #4)
> It seems that at least Thomas and Dominique believe that this can be closed.

with which status?
>From gcc-bugs-return-630132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 02:25:08 2019
Return-Path: <gcc-bugs-return-630132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28707 invoked by alias); 22 Jan 2019 02:24:53 -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 26087 invoked by uid 48); 22 Jan 2019 02:24:48 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] New: [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 02:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88964-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: 2019-01/txt/msg02941.txt.bz2
Content-length: 4379

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

            Bug ID: 88964
           Summary: [8/9 Regression] ICE in wide_int_to_tree_1, at
                    tree.c:1561
           Product: gcc
           Version: 8.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gfortran-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the
following snippet reduced from gcc/testsuite/gfortran.dg/pr68251.f90 w/ -O3
-fno-tree-forwprop --param sccvn-max-alias-queries-per-access=1:

MODULE hfx_contract_block
  INTEGER, PARAMETER :: dp=8
CONTAINS
  SUBROUTINE
contract_block(ma_max,mb_max,mc_max,md_max,kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
    REAL(KIND=dp) :: kbd(mb_max*md_max), kbc(mb_max*mc_max), &
      kad(ma_max*md_max), kac(ma_max*mc_max), pbd(mb_max*md_max), &
      pbc(mb_max*mc_max), pad(ma_max*md_max), pac(ma_max*mc_max), &
      prim(ma_max*mb_max*mc_max*md_max), scale
    CALL block_1_3_1_3(kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
    CALL block_1_3_1_4(kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
    CALL block_1_3_1_5(kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
  END SUBROUTINE contract_block
  SUBROUTINE block_1_3_1_3(kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
    REAL(KIND=dp) :: kbd(3*3), kbc(3*1), kad(1*3), kac(1*1), pbd(3*3), &
      pbc(3*1), pad(1*3), pac(1*1), prim(1*3*1*3), scale
      DO md = 1,3
        DO mc = 1,1
          DO mb = 1,3
            DO ma = 1,1
              kac((mc-1)*1+ma) = kac((mc-1)*1+ma)-tmp*p_bd
            END DO
          END DO
        END DO
      END DO
  END SUBROUTINE block_1_3_1_3
  SUBROUTINE block_1_3_1_4(kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
    REAL(KIND=dp) :: kbd(3*4), kbc(3*1), kad(1*4), kac(1*1), pbd(3*4), &
      pbc(3*1), pad(1*4), pac(1*1), prim(1*3*1*4), scale
      DO md = 1,4
        DO mc = 1,1
          DO mb = 1,3
            kbc((mc-1)*3+mb) = kbc((mc-1)*3+mb) - ks_bc
          END DO
        END DO
      END DO
  END SUBROUTINE block_1_3_1_4
  SUBROUTINE block_1_3_1_5(kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
    REAL(KIND=dp) :: kbd(3*5), kbc(3*1), kad(1*5), kac(1*1), pbd(3*5), &
      pbc(3*1), pad(1*5), pac(1*1), prim(1*3*1*5), scale
      DO md = 1,5
        DO mc = 1,1
          DO mb = 1,3
            DO ma = 1,1
              kac((mc-1)*1+ma) = kac((mc-1)*1+ma)-tmp*p_bd
            END DO
          END DO
        END DO
      END DO
  END SUBROUTINE block_1_3_1_5
END MODULE hfx_contract_block

% powerpc-e300c3-linux-gnu-gfortran-9.0.0-alpha20190120 -O3 -fno-tree-forwprop
--param sccvn-max-alias-queries-per-access=1 -c cn013jaw.f90
during GIMPLE pass: linterchange
cn013jaw.f90:4:0:

    4 |   SUBROUTINE
contract_block(ma_max,mb_max,mc_max,md_max,kbd,kbc,kad,kac,pbd,pbc,pad,pac,prim,scale)
      | 
internal compiler error: in wide_int_to_tree_1, at tree.c:1561
0x6befc2 wide_int_to_tree_1
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.c:1561
0x106439e build_int_cst(tree_node*, poly_int<1u, long>)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.c:1355
0x149f832 loop_cand::analyze_induction_var(tree_node*, tree_node*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-loop-interchange.cc:695
0x149fd58 loop_cand::analyze_carried_vars(loop_cand*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-loop-interchange.cc:752
0x14a2195 tree_loop_interchange::interchange(vec<data_reference*, va_heap,
vl_ptr>, vec<data_dependence_relation*, va_heap, vl_ptr>)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-loop-interchange.cc:1600
0x14a2dcf execute
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-loop-interchange.cc:2070

(While my target here is powerpc, the ICE is not target-specific.)
>From gcc-bugs-return-630133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 02:27:50 2019
Return-Path: <gcc-bugs-return-630133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58681 invoked by alias); 22 Jan 2019 02:27:49 -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 58654 invoked by uid 48); 22 Jan 2019 02:27:45 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 02:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: cf_known_to_work cf_known_to_fail
Message-ID: <bug-88964-4-2IXyJAlJr3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg02942.txt.bz2
Content-length: 536

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

Arseny Solokha <asolokha at gmx dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |7.3.0
      Known to fail|                            |8.2.0, 9.0

--- Comment #1 from Arseny Solokha <asolokha at gmx dot com> ---
The pass in question was introduced in gcc 8 so I'm not sure if this PR really
deserves to be marked as regression.
>From gcc-bugs-return-630134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 02:31:23 2019
Return-Path: <gcc-bugs-return-630134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75582 invoked by alias); 22 Jan 2019 02:31:05 -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 73255 invoked by uid 55); 22 Jan 2019 02:31:01 -0000
From: "amodra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88614] ICE: output_operand: invalid %z value
Date: Tue, 22 Jan 2019 02:31: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amodra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88614-4-eQHJMNZaeS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88614-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88614-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: 2019-01/txt/msg02943.txt.bz2
Content-length: 3605

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

--- Comment #3 from Alan Modra <amodra at gcc dot gnu.org> ---
Author: amodra
Date: Tue Jan 22 02:29:47 2019
New Revision: 268135

URL: https://gcc.gnu.org/viewcvs?rev=268135&root=gcc&view=rev
Log:
[RS6000] PR88614, output_operand: invalid %z value

The direct cause of this PR is the fact that tls_gdld_nomark didn't
handle indirect calls.  Also, most indirect calls were being optimised
back to direct calls anyway, due to tls_gdld_nomark not checking any
of the parallel elements except the first (plus the extra element that
distinguishes this call from normal calls).  There were other unwanted
substitutions too.

So this patch attacks the problem of handling special calls in a
different way.  Rather than adding another element to the call insn
parallel to distinguish -mno-tls-markers __tls_get_addr calls from any
other calls, we now inspect the second CALL arg.  Each
call_value_nonlocal and call_value_indirect insn now checks for the
tlsgd/ld unspecs when !TARGET_TLS_MARKERS and emits the arg setup
insns.  I disallow the local call patterns since we'll only see local
calls to __tls_get_addr in testcases, and it doesn't seem a good idea
to complicate the patterns just for a minor optimisation.  Sibling
call insns aren't used for libcalls, so none of these insns need to
change.

The patch also fixes a minor problem with -mno-tls-markers
__tls_get_addr calls causing a "li 3,0" instruction to be emitted
prior to the arg setup instructions, due to using a libcall with one
arg.  That isn't correct when the call insn itself sets up its arg.
Also, I've tidied the V4 secure-plt calls, generating them in
rs6000_call_sysv rather than by splitting in rs6000.md.  The
CALL_INSN_FUNCTION_USAGE added in edit_tls_call_insn is no longer
needed (since git commit 0a4b5c66df9).

On the subject of unwanted substitutions, I also saw a
_GLOBAL_OFFSET_TABLE_ symbol_ref being substituted for the GOT reg,
resulting in code like "addi 3,_GLOBAL_OFFSET_TABLE_,tls_ld@got@tlsld".
Fixed by the unspec_tls change.

        PR target/88614
        * config/rs6000/predicates.md (unspec_tls): Ensure GOT reg
        stays a reg.  Allow a const_int.
        * config/rs6000/rs6000-protos.h (rs6000_output_tlsargs): Declare.
        * config/rs6000/rs6000.h (IS_V4_FP_ARGS): Define.
        (IS_NOMARK_TLSGETADDR): Define.
        * config/rs6000/rs6000.c (edit_tls_call_insn): Delete.
        (rs6000_output_tlsargs): New function.
        (rs6000_legitimize_tls_address): Don't say a !TARGET_TLS_MARKERS
        __tls_get_addr call takes an arg.
        (rs6000_call_sysv): Generate sysv4 secure plt call pattern here..
        * config/rs6000/rs6000.md (call_nonlocal_sysv): ..rather than here,
        delete split..
        (call_value_nonlocal_sysv): ..or here, delete split.
        (tls_gdld_nomark): Delete.
        (call_value_indirect_nonlocal_sysv): Use unspec_tls as operand2
        predicate.  Call rs6000_output_tlsargs.  Adjust length to suit.
        (call_value_nonlocal_sysv): Likewise.
        (call_value_nonlocal_sysv_secure): Likewise.
        (call_value_nonlocal_aix): Likewise.
        (call_value_indirect_aix): Likewise.
        (call_value_indirect_elfv2): Likewise.
        (call_value_local32, call_value_local64): Disable for no-mark tls.
        (call_value_local_aix): Likewise.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/rs6000/predicates.md
    trunk/gcc/config/rs6000/rs6000-protos.h
    trunk/gcc/config/rs6000/rs6000.c
    trunk/gcc/config/rs6000/rs6000.h
    trunk/gcc/config/rs6000/rs6000.md
>From gcc-bugs-return-630135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 02:40:56 2019
Return-Path: <gcc-bugs-return-630135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49709 invoked by alias); 22 Jan 2019 02:40:55 -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 49602 invoked by uid 48); 22 Jan 2019 02:40:51 -0000
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88614] ICE: output_operand: invalid %z value
Date: Tue, 22 Jan 2019 02:40: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amodra at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-88614-4-WYo4hFhivZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88614-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88614-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: 2019-01/txt/msg02944.txt.bz2
Content-length: 476

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

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |9.0

--- Comment #4 from Alan Modra <amodra at gmail dot com> ---
Patch applied.
>From gcc-bugs-return-630136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 03:16:12 2019
Return-Path: <gcc-bugs-return-630136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89976 invoked by alias); 22 Jan 2019 03:16:11 -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 89895 invoked by uid 48); 22 Jan 2019 03:16:05 -0000
From: "anton at samba dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] New: powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 03:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anton at samba dot org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-88965-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: 2019-01/txt/msg02945.txt.bz2
Content-length: 1245

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

            Bug ID: 88965
           Summary: powerpc64le vector builtin hits ICE in verify_gimple
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: anton at samba dot org
                CC: segher at gcc dot gnu.org, wschmidt at gcc dot gnu.org
  Target Milestone: ---
            Target: powerpc64le-linux

The following (admittedly odd) code results in an ICE on trunk, target
powerpc64le:

unsigned int a[1];
void b(void) { __builtin_vec_vsx_ld(0, &a[0]); }

...

blake.i: In function 'b':
blake.i:2:6: error: invalid address operand in MEM_REF
    2 | void b(void) { __builtin_vec_vsx_ld(0, &a[0]); }
      |      ^
MEM[(void *)&a[0]];

_1 = MEM[(void *)&a[0]];
during GIMPLE pass: lower
blake.i:2:6: internal compiler error: verify_gimple failed
0x10a7ddfb verify_gimple_in_seq(gimple*)
    ../../gcc/gcc/tree-cfg.c:5082
0x108dcff7 execute_function_todo
    ../../gcc/gcc/passes.c:1979
0x108de5bb do_per_function
    ../../gcc/gcc/passes.c:1638
0x108de7cb execute_todo
    ../../gcc/gcc/passes.c:2031
>From gcc-bugs-return-630137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 04:03:28 2019
Return-Path: <gcc-bugs-return-630137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92196 invoked by alias); 22 Jan 2019 04:03:27 -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 92108 invoked by uid 48); 22 Jan 2019 04:03:23 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Tue, 22 Jan 2019 04:03: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88954-4-BYJuG3TKEx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg02946.txt.bz2
Content-length: 1199

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

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
My question is about the change you are proposing.  How do you expect g() to be
called if the test case from comment #0 is modified for example as follows:

  void f_plt(void);
  void f_noplt(void) __attribute__((noplt));
  void (*p_noplt)(void) = f_noplt;
  void g(void (*)(void));

  int main()
  {
    if (getenv ("USE_PLT"))
      p_noplt = f_plt;   // should this be diagnosed?

    g (p_noplt);
  }

In most other cases, initializing a pointer with the address of a function
declared with some function attribute (e.g., const, nonnull, noreturn, pure, or
warn_unused_result) doesn't transfer the special properties to the pointer, so
I'm trying to understand what semantics you are after and if there is any
potential for user errors and decide whether they should be detected.

I happen to think it would make sense to make it possible to imbue function
pointers with some (but not all) of the same attributes as those that apply to
functions, but there certainly are cases where doing so could cause problems,
just as there are cases where not doing so can.
>From gcc-bugs-return-630138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 04:12:30 2019
Return-Path: <gcc-bugs-return-630138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47378 invoked by alias); 22 Jan 2019 04:12:30 -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 38395 invoked by uid 48); 22 Jan 2019 04:12:25 -0000
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Tue, 22 Jan 2019 04:12: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amodra at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88877-4-iM2FpkXyVT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg02947.txt.bz2
Content-length: 630

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

--- Comment #17 from Alan Modra <amodra at gmail dot com> ---
> Is anything broken though?

Yes, as demonstrated by the testcase.

> If the libcall routines know they are called this way, all is fine.

They don't.  libgcc functions are mostly C code that can make use of the fact
that on ppc64 an unsigned int arg will have the top 32 bits zeroed.

We avoid some potential problems with things like popcount by not having a
popcountsi.  Instead we use popcountdi, and that results in gcc zero-extending
a 32-bit value to 64 bits before we reach emit_library_call_value_1.
>From gcc-bugs-return-630139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 04:25:47 2019
Return-Path: <gcc-bugs-return-630139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62425 invoked by alias); 22 Jan 2019 04:25: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 62311 invoked by uid 48); 22 Jan 2019 04:25:41 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/44317] ,##__VA_ARGS__ comma not eaten with -std=c++0x
Date: Tue, 22 Jan 2019 04:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.4.4
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-44317-4-horApmiQjV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44317-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44317-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: 2019-01/txt/msg02948.txt.bz2
Content-length: 163

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

--- Comment #11 from emsr at gcc dot gnu.org ---
The work for preprocessor/83063 may have impacted this bug.
>From gcc-bugs-return-630140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 04:27:36 2019
Return-Path: <gcc-bugs-return-630140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65064 invoked by alias); 22 Jan 2019 04:27:34 -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 64830 invoked by uid 48); 22 Jan 2019 04:27:30 -0000
From: "bmeng.cn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88966] New: Indirect stringification of "linux" produces "1"
Date: Tue, 22 Jan 2019 04:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bmeng.cn at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88966-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: 2019-01/txt/msg02949.txt.bz2
Content-length: 2417

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

            Bug ID: 88966
           Summary: Indirect stringification of "linux" produces "1"
           Product: gcc
           Version: 5.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bmeng.cn at gmail dot com
  Target Milestone: ---

Created attachment 45487
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45487&action=edit
test case

This issue is seen with GCC 5.4.0 shipped by Ubuntu 16.04, but is also
reproducible with GCC 7.3.0 and 8.1.0.

Use attached test case (test.c) to reproduce.

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
5.4.0-6ubuntu1~16.04.10' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-5 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 

$ gcc test.c -o test
$ ./test
case 1: 1
case 2: vmlinux
case 3: linux4.20
case 4: weird 1 ?
case 5: linux

It looks the indirect stringification (two levels) has special handling of
"linux". Doing just one level (see case 5) works fine.
>From gcc-bugs-return-630141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 04:29:34 2019
Return-Path: <gcc-bugs-return-630141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67546 invoked by alias); 22 Jan 2019 04:29:34 -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 67465 invoked by uid 48); 22 Jan 2019 04:29:29 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86756] Don't define __cpp_lib_filesystem unless --enable-libstdcxx-filesystem-ts
Date: Tue, 22 Jan 2019 04:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86756-4-0dSUcZP7Rz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86756-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: 2019-01/txt/msg02950.txt.bz2
Content-length: 737

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

sandra at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sandra at gcc dot gnu.org

--- Comment #6 from sandra at gcc dot gnu.org ---
The patch for this issue seems to have caused several test regressions and new
failures on nios2-elf, a newlib-based target with semihosted i/o.  It's getting
link-time errors about references to undefined symbols chdir, mkdir, etc.

It's not clear how I'm supposed to fix that.  Am I missing some configure
option, or should I be adding dg-skip-if (or whatever) to the failing tests?
>From gcc-bugs-return-630142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 04:55:17 2019
Return-Path: <gcc-bugs-return-630142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29437 invoked by alias); 22 Jan 2019 04:55:16 -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 29368 invoked by uid 48); 22 Jan 2019 04:55:12 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Tue, 22 Jan 2019 04:55: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88954-4-NkqjuNfu7c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg02951.txt.bz2
Content-length: 1613

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

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Martin Sebor from comment #3)
> My question is about the change you are proposing.  How do you expect g() to
> be called if the test case from comment #0 is modified for example as
> follows:
> 
>   void f_plt(void);
>   void f_noplt(void) __attribute__((noplt));
>   void (*p_noplt)(void) = f_noplt;
>   void g(void (*)(void));
> 
>   int main()
>   {
>     if (getenv ("USE_PLT"))
>       p_noplt = f_plt;   // should this be diagnosed?

f_plt will be handled by

000000404020  000600000007 R_X86_64_JUMP_SLO 0000000000401040 f_plt + 0

>     g (p_noplt);
>   }
> 
> In most other cases, initializing a pointer with the address of a function
> declared with some function attribute (e.g., const, nonnull, noreturn, pure,
> or warn_unused_result) doesn't transfer the special properties to the
> pointer, so I'm trying to understand what semantics you are after and if
> there is any potential for user errors and decide whether they should be
> detected.
> 
> I happen to think it would make sense to make it possible to imbue function
> pointers with some (but not all) of the same attributes as those that apply
> to functions, but there certainly are cases where doing so could cause
> problems, just as there are cases where not doing so can.

__attribute__((noplt)) only applies to functions, which instructors
compiler to avoid PLT when accessing the marked function, via function
pointer nor direct call.  The function pointer itself has no impact
on PLT.
>From gcc-bugs-return-630143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 05:05:08 2019
Return-Path: <gcc-bugs-return-630143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42373 invoked by alias); 22 Jan 2019 05:05:06 -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 42272 invoked by uid 48); 22 Jan 2019 05:05:02 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 05:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-n0Vd1DYL3m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg02952.txt.bz2
Content-length: 821

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

--- Comment #19 from Chris Elrod <elrodc at gmail dot com> ---
To add a little more:
I used inline asm for direct access to the rsqrt instruction "vrsqrt14ps" in
Julia. Without adding a Newton step, the answers are wrong beyond just a couple
significant digits.
With the Newton step, the answers are correct.

My point is that LLVM-compiled code (Clang/Flang/ispc) are definitely adding
the Newton step. They get the correct answer.

That leaves my best guess for the performance difference as owing to the masked
"vrsqrt14ps" that gcc is using:

        vcmpps  $4, %zmm0, %zmm5, %k1
        vrsqrt14ps      %zmm0, %zmm1{%k1}{z}

Is there any way for me to test that idea?
Edit the asm to remove the vcmppss and mask, compile the asm with gcc, and
benchmark it?
>From gcc-bugs-return-630144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 05:16:58 2019
Return-Path: <gcc-bugs-return-630144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121089 invoked by alias); 22 Jan 2019 05:16:57 -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 121042 invoked by uid 48); 22 Jan 2019 05:16:53 -0000
From: "dinuxbg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88966] Indirect stringification of "linux" produces "1"
Date: Tue, 22 Jan 2019 05:16: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: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinuxbg at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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-88966-4-rscg8WBU1k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88966-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: 2019-01/txt/msg02953.txt.bz2
Content-length: 506

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

Dimitar Dimitrov <dinuxbg at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dinuxbg at gmail dot com

--- Comment #1 from Dimitar Dimitrov <dinuxbg at gmail dot com> ---
The "linux" is a predefined macro:

$ $ gcc -E -dM - </dev/null|grep -w linux
#define linux 1

Looks like by-design to me.
>From gcc-bugs-return-630145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 05:25:14 2019
Return-Path: <gcc-bugs-return-630145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128598 invoked by alias); 22 Jan 2019 05:25:13 -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 128513 invoked by uid 48); 22 Jan 2019 05:25:08 -0000
From: "bmeng.cn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88966] Indirect stringification of "linux" produces "1"
Date: Tue, 22 Jan 2019 05:25: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: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bmeng.cn at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88966-4-SxyOTuY3Oc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88966-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: 2019-01/txt/msg02954.txt.bz2
Content-length: 409

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

--- Comment #2 from Bin Meng <bmeng.cn at gmail dot com> ---
(In reply to Dimitar Dimitrov from comment #1)
> The "linux" is a predefined macro:
> 
> $ $ gcc -E -dM - </dev/null|grep -w linux
> #define linux 1
> 
> Looks like by-design to me.

Indeed "linux" is a predefined macro. But why does str(linux) and
stringify(linux) give different results?
>From gcc-bugs-return-630146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 05:34:38 2019
Return-Path: <gcc-bugs-return-630146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7457 invoked by alias); 22 Jan 2019 05:34: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 7412 invoked by uid 48); 22 Jan 2019 05:34:34 -0000
From: "anton at samba dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 05:34: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anton at samba dot org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88965-4-sUjac3pixu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg02955.txt.bz2
Content-length: 775

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

--- Comment #1 from Anton Blanchard <anton at samba dot org> ---
Here's something more representative. Passing the address via an explicit
pointer makes the issue go away.


#include <stdint.h>
#include <altivec.h>

#define LOADU(p)        vec_vsx_ld(0, (vector unsigned long *)(p))

static uint64_t blake2b_IV[8] =
{
        0x6a09e667f3bcc908ULL, 0xbb67ae8584caa73bULL,
        0x3c6ef372fe94f82bULL, 0xa54ff53a5f1d36f1ULL,
        0x510e527fade682d1ULL, 0x9b05688c2b3e6c1fULL,
        0x1f83d9abfb41bd6bULL, 0x5be0cd19137e2179ULL
};

vector unsigned long ret;

int main(void)
{
#ifdef GOOD
        unsigned long *p = &blake2b_IV[0];

        ret = LOADU(p);
#else
        ret = LOADU(&blake2b_IV[0]);
#endif
}
>From gcc-bugs-return-630147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 05:40:53 2019
Return-Path: <gcc-bugs-return-630147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20030 invoked by alias); 22 Jan 2019 05:40:52 -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 19938 invoked by uid 48); 22 Jan 2019 05:40:48 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 05:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-Jc79v1ZUbB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg02956.txt.bz2
Content-length: 2420

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

--- Comment #20 from Chris Elrod <elrodc at gmail dot com> ---
To add a little more:
I used inline asm for direct access to the rsqrt instruction "vrsqrt14ps" in
Julia. Without adding a Newton step, the answers are wrong beyond just a couple
significant digits.
With the Newton step, the answers are correct.

My point is that LLVM-compiled code (Clang/Flang/ispc) are definitely adding
the Newton step. They get the correct answer.

That leaves my best guess for the performance difference as owing to the masked
"vrsqrt14ps" that gcc is using (g++ does this too):

        vcmpps  $4, %zmm0, %zmm5, %k1
        vrsqrt14ps      %zmm0, %zmm1{%k1}{z}

Is there any way for me to test that idea?
Edit the asm to remove the vcmppss and mask, compile the asm with gcc, and
benchmark it?


Okay, I just tried playing around with flags and looking at asm.
I compiled with:

g++ -O3 -ffinite-math-only -fexcess-precision=fast -fno-math-errno
-fno-signed-zeros -fno-trapping-math -fassociative-math -freciprocal-math
-fno-rounding-math -fno-signaling-nans -march=native -shared -fPIC
-mprefer-vector-width=512 -fno-semantic-interposition -o
libgppvectorization_test.so  vectorization_test.cpp

which is basically all flags implied by "-ffast-math", except
"-funsafe-math-optimizations". This does include the flags implied by the
unsafe-math optimizations, just not that flag itself.

This list can be simplified to (only "-fno-math-errno" is needed):

g++ -O3 -fno-math-errno -march=native -shared -fPIC -mprefer-vector-width=512
-fno-semantic-interposition -o libgppvectorization_test.so 
vectorization_test.cpp

or

gfortran -O3 -fno-math-errno -march=native -shared -fPIC
-mprefer-vector-width=512 -fno-semantic-interposition -o
libgfortvectorization_test.so  vectorization_test.f90

This results in the following:

        vsqrtps (%r8,%rax), %zmm0
        vdivps  %zmm0, %zmm7, %zmm0

ie, vsqrt and a division, rather than the masked reciprocal square root.

With N = 2827, that speeds gfortran and g++ from about 4.3 microseconds to 3.5
microseconds.
For comparison, Clang takes about 2 microseconds, and Flang/ispc/and awful
looking unsafe Rust take 2.3-2.4 microseconds, using the vrsqrt14ps (without a
mask) and a Newton step, instead of vsqrtps followed by a division.


So, "-funsafe-math-optimizations" results in a regression here.
>From gcc-bugs-return-630148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 06:57:37 2019
Return-Path: <gcc-bugs-return-630148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80578 invoked by alias); 22 Jan 2019 06:57:37 -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 80524 invoked by uid 48); 22 Jan 2019 06:57:33 -0000
From: "d25fe0be at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88475] -E -fdirectives-only clashes with raw strings
Date: Tue, 22 Jan 2019 06:57: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: d25fe0be at outlook dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88475-4-CRIhGDiGIo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88475-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: 2019-01/txt/msg02957.txt.bz2
Content-length: 236

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

--- Comment #2 from d25fe0be@ <d25fe0be at outlook dot com> ---
It looks like this was (incorrectly, I assume) rejected since GCC 4.4.

https://wandbox.org/permlink/I0yF3U3OXoH6LbIM
>From gcc-bugs-return-630149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:03:40 2019
Return-Path: <gcc-bugs-return-630149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110277 invoked by alias); 22 Jan 2019 07:03:40 -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 110218 invoked by uid 48); 22 Jan 2019 07:03:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88961] valgrind error in resolve_ref
Date: Tue, 22 Jan 2019 07:03: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88961-4-jDSVGg7Rww@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88961-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: 2019-01/txt/msg02958.txt.bz2
Content-length: 393

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Dup of PR88871?
>From gcc-bugs-return-630151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:28:56 2019
Return-Path: <gcc-bugs-return-630151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22197 invoked by alias); 22 Jan 2019 07:28:56 -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 22128 invoked by uid 48); 22 Jan 2019 07:28:51 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88961] valgrind error in resolve_ref
Date: Tue, 22 Jan 2019 07:28: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88961-4-5NINHloho1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88961-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: 2019-01/txt/msg02960.txt.bz2
Content-length: 734

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2019-01-22
                 CC|                            |tkoenig at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> Dup of PR88871?

Displays the same symptoms.

What version exactly? Is it before r268092?  What happens if you
upgrade to current trunk?
>From gcc-bugs-return-630150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:28:02 2019
Return-Path: <gcc-bugs-return-630150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20897 invoked by alias); 22 Jan 2019 07:28:01 -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 20852 invoked by uid 48); 22 Jan 2019 07:27:57 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/88967] New: [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 07:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: objc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88967-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: 2019-01/txt/msg02959.txt.bz2
Content-length: 1397

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

            Bug ID: 88967
           Summary: [9 regression] openmp default(none) broken
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: objc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: lebedev.ri at gmail dot com
  Target Milestone: ---

https://godbolt.org/z/8WHddH

void foo(int *x);

void test1(int * const begin, const int len) {
#pragma omp parallel default(none)
#pragma omp for
for(int x = 0; x < len; x++)
    foo(begin + x);
}

gcc 8.2, clang trunk is ok with that code.
gcc trunk says:

<source>: In function 'void test1(int*, int)':
<source>:5:9: error: 'len' not specified in enclosing 'parallel'
    5 | #pragma omp for
      |         ^~~
<source>:4:9: error: enclosing 'parallel'
    4 | #pragma omp parallel default(none)
      |         ^~~
<source>:7:9: error: 'begin' not specified in enclosing 'parallel'
    7 |     foo(begin + x);
      |         ^~~~~
<source>:4:9: error: enclosing 'parallel'
    4 | #pragma omp parallel default(none)
      |         ^~~
Compiler returned: 1

Since 'default(none)' is specified, i fail to see how they are not specified..

I'm also not really seeing the reasoning in the openmp 4.0 "2.14.3.1 default
clause".
Did this change in newer openmp versions?
>From gcc-bugs-return-630152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:44:54 2019
Return-Path: <gcc-bugs-return-630152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129864 invoked by alias); 22 Jan 2019 07:44:53 -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 129840 invoked by uid 48); 22 Jan 2019 07:44:49 -0000
From: "linux at carewolf dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88475] -E -fdirectives-only clashes with raw strings
Date: Tue, 22 Jan 2019 07:44: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linux at carewolf dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88475-4-cPoOPSVIbW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88475-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: 2019-01/txt/msg02961.txt.bz2
Content-length: 208

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

--- Comment #3 from Allan Jensen <linux at carewolf dot com> ---
No, it has to be a raw-string to be valid.
https://wandbox.org/permlink/I0yF3U3OXoH6LbIM
>From gcc-bugs-return-630153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:49:31 2019
Return-Path: <gcc-bugs-return-630153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6746 invoked by alias); 22 Jan 2019 07:49:29 -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 6667 invoked by uid 48); 22 Jan 2019 07:49:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 07:49: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
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: bug_status resolution
Message-ID: <bug-88967-4-6q1DD7xBGA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg02962.txt.bz2
Content-length: 2305

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It indeed changed, already in OpenMP 4.0 actually, but I've been long hoping
that the change will be reverted in later OpenMP standards, in the end that is
not what is going to happen.
OpenMP 3.1 and earlier had:
"Variables with const-qualified type having no mutable member are shared."
among the predetermined data sharing of variables for C/C++, and
"Variables with const-qualified type having no mutable member may be listed in
a
C/C++ firstprivate clause."
as an exception to the rule that variables with predetermined data sharing may
not be specified in OpenMP data sharing clauses.
That is gone in OpenMP 4.0, these variables are not predetermined anymore, so
with default(none) they must be specified in data sharing clauses if they are
referenced in the region.  They can be specified in both shared and
firstprivate clauses now, e.g. lastprivate/reduction/linear aren't suitable
because they all need to write into the variable.  If you want to write code
that will work with both OpenMP 3.1 and OpenMP 4.0+ (including 5.0, which
hasn't changed in this area), you need to use firstprivate(begin, len) in your
example, that used to be valid in OpenMP 3.1 due to the above exception and
keeps to be valid now.

I've asked the ifort/clang maintainers about why they keep violating the
standard, but haven't heard back from them.  And I must say I was trying hard
to readd the above rule + exception, but haven't succeeded.

The exact wording why the above needs to be refused is:
"The default(none) clause requires that each variable that is referenced in the
construct, and that does not have a predetermined data-sharing attribute, must
have its data-sharing attribute explicitly determined by being listed in a
data-sharing attribute clause."
As it is not predetermined (anymore) and is not explicitly determined either,
it violates the requirement above.
>From gcc-bugs-return-630154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:54:56 2019
Return-Path: <gcc-bugs-return-630154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18977 invoked by alias); 22 Jan 2019 07:54:55 -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 18816 invoked by uid 48); 22 Jan 2019 07:54:51 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 07:54: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail 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-88967-4-H8ceEAzrWT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg02963.txt.bz2
Content-length: 405

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

--- Comment #2 from Roman Lebedev <lebedev.ri at gmail dot com> ---
(In reply to Jakub Jelinek from comment #1)
> It indeed changed, already in OpenMP 4.0 actually, but I've been long hoping
> that the change will be reverted in later OpenMP standards, in the end that
> is not what is going to happen.
> ...

Sigh!
Ok, thank you for the reply :/
>From gcc-bugs-return-630155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:57:58 2019
Return-Path: <gcc-bugs-return-630155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27715 invoked by alias); 22 Jan 2019 07:57:57 -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 26243 invoked by uid 48); 22 Jan 2019 07:57:53 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 07:57: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail 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-88967-4-kkYuUPv95T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg02964.txt.bz2
Content-length: 366

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

--- Comment #3 from Roman Lebedev <lebedev.ri at gmail dot com> ---
While there, any advice on how that is supposed to be rewritten?
Simply adding "shared(begin, len)" makes older gcc's unhappy
https://godbolt.org/z/gyZBR-
Only keeping "shared(begin, len)" (and dropping "default(none)") does not work
either.
>From gcc-bugs-return-630157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:58:17 2019
Return-Path: <gcc-bugs-return-630157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30338 invoked by alias); 22 Jan 2019 07:58:17 -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 29621 invoked by uid 48); 22 Jan 2019 07:58:12 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88969] New: ICE in build_op_delete_call, at cp/call.c:6509
Date: Tue, 22 Jan 2019 07:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88969-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: 2019-01/txt/msg02966.txt.bz2
Content-length: 4478

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

            Bug ID: 88969
           Summary: ICE in build_op_delete_call, at cp/call.c:6509
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
snippet reduced from test/SemaCXX/cxx2a-destroying-delete.cpp from clang 7.0.1
test suite:

namespace std {
  struct destroying_delete_t {
    struct __construct { explicit __construct() = default; };
  };
}

namespace delete_selection {
  struct B {
    void operator delete(void*) = delete;
    void operator delete(B *, std::destroying_delete_t) = delete;
  };
  void delete_B(B *b) { delete b; }
}

% g++-9.0.0-alpha20190120 -c mi9qy2yt.cpp
mi9qy2yt.cpp: In function 'void
delete_selection::delete_B(delete_selection::B*)':
mi9qy2yt.cpp:12:32: internal compiler error: in build_op_delete_call, at
cp/call.c:6509
   12 |   void delete_B(B *b) { delete b; }
      |                                ^
0x5b81f3 build_op_delete_call(tree_code, tree_node*, tree_node*, bool,
tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/call.c:6509
0x9454d8 build_delete(tree_node*, tree_node*, special_function_kind, int, int,
int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/init.c:4825
0x9b6036 cp_parser_unary_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:8196
0x98eb02 cp_parser_cast_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:9345
0x98f3da cp_parser_binary_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:9447
0x990546 cp_parser_assignment_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:9744
0x99091a cp_parser_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:9911
0x993e95 cp_parser_expression_statement
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11449
0x99f578 cp_parser_statement
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11245
0x9a0c38 cp_parser_statement_seq_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11592
0x9a0d18 cp_parser_compound_statement
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11546
0x9bab16 cp_parser_function_body
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:22530
0x9bab16 cp_parser_ctor_initializer_opt_and_function_body
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:22567
0x9bb3f0 cp_parser_function_definition_after_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27630
0x9bc1d4 cp_parser_function_definition_from_specifiers_and_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27546
0x9bc1d4 cp_parser_init_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:20205
0x99d518 cp_parser_simple_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13476
0x9c2cdd cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13173
0x9c389c cp_parser_declaration_seq_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13049
0x9c389c cp_parser_namespace_body
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:19252
>From gcc-bugs-return-630156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:58:12 2019
Return-Path: <gcc-bugs-return-630156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28960 invoked by alias); 22 Jan 2019 07:58: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 28506 invoked by uid 48); 22 Jan 2019 07:58:07 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88968] New: [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 07:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88968-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: 2019-01/txt/msg02965.txt.bz2
Content-length: 1857

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

            Bug ID: 88968
           Summary: [8/9 Regression] Stack overflow in gimplify_expr
           Product: gcc
           Version: 8.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, openmp
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gcc-9.0.0-alpha20190120 snapshot (r268107) demonstrates stack overflow when
compiling the following snippet w/ -fopenmp:

struct {
  unsigned int hq : 16;
  unsigned int dv : 1;
} __attribute__ ((__packed__)) e2;

void
yp (void)
{
#pragma omp atomic
  ++e2.hq;
}

% gcc-9.0.0-alpha20190120 -fopenmp -c gqqutwbw.c
gcc-9.0.0-alpha20190120: internal compiler error: Segmentation fault signal
terminated program cc1

==18746== Stack overflow in thread #1: can't grow stack to 0x1ffe001000
==18746== Can't extend stack to 0x1ffe000fd8 during signal delivery for thread
1:
==18746==   no stack segment
==18746== 
==18746== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==18746==  Access not within mapped region at address 0x1FFE000FD8
==18746== Stack overflow in thread #1: can't grow stack to 0x1ffe001000
==18746==    at 0xAE6E4B: gimplify_expr(tree_node**, gimple**, gimple**, bool
(*)(tree_node*), int) (gimplify.c:13292)
==18746==  If you believe this happened as a result of a stack
==18746==  overflow in your program's main thread (unlikely but
==18746==  possible), you can try to increase the size of the
==18746==  main thread stack using the --main-stacksize= flag.
==18746==  The main thread stack size used in this run was 16777216.
>From gcc-bugs-return-630158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 07:58:27 2019
Return-Path: <gcc-bugs-return-630158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33474 invoked by alias); 22 Jan 2019 07:58:26 -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 31259 invoked by uid 48); 22 Jan 2019 07:58:22 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88970] New: ICE: verify_ssa failed (error: definition in block 2 follows the use)
Date: Tue, 22 Jan 2019 07:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88970-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: 2019-01/txt/msg02967.txt.bz2
Content-length: 1560

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

            Bug ID: 88970
           Summary: ICE: verify_ssa failed (error: definition in block 2
                    follows the use)
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
snippet:

template <typename T> int
b (T);

void
d ()
{
  typedef int e[b (1)];
  e f;
  int c;

  [&]
  {
    c = sizeof (f);
    [&]
    {
      c = sizeof (f);
    } ();
  } ();
}

% g++-9.0.0-alpha20190120 -c tc1ytzqq.cpp
tc1ytzqq.cpp: In lambda function:
tc1ytzqq.cpp:19:1: error: definition in block 2 follows the use
   19 | }
      | ^
for SSA_NAME: _1 in statement:
_1 = _1 + 1;
during GIMPLE pass: ssa
tc1ytzqq.cpp:19:1: internal compiler error: verify_ssa failed
0x11be57f verify_ssa(bool, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-ssa.c:1188
0xebec5d execute_function_todo
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:1984
0xebfa5e execute_todo
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:2031

But it may have a number of duplicates alreadyâ€¦
>From gcc-bugs-return-630159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:03:33 2019
Return-Path: <gcc-bugs-return-630159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80152 invoked by alias); 22 Jan 2019 08:03:32 -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 80120 invoked by uid 48); 22 Jan 2019 08:03:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88970] ICE: verify_ssa failed (error: definition in block 2 follows the use)
Date: Tue, 22 Jan 2019 08:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88970-4-fvfB3w9MUs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88970-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88970-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: 2019-01/txt/msg02968.txt.bz2
Content-length: 595

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, it's very old (at least 4.9.0).
>From gcc-bugs-return-630160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:03:59 2019
Return-Path: <gcc-bugs-return-630160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81068 invoked by alias); 22 Jan 2019 08:03:59 -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 80994 invoked by uid 48); 22 Jan 2019 08:03:55 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 08:03: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail 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-88967-4-mVZSosQSBz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg02969.txt.bz2
Content-length: 552

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

--- Comment #4 from Roman Lebedev <lebedev.ri at gmail dot com> ---
(In reply to Roman Lebedev from comment #3)
> While there, any advice on how that is supposed to be rewritten?
> Simply adding "shared(begin, len)" makes older gcc's unhappy
> https://godbolt.org/z/gyZBR-
> Only keeping "shared(begin, len)" (and dropping "default(none)") does not
> work either.

Right, "firstprivate(begin, len)" works while being backward compatible,
sorry for panicking too early.
https://godbolt.org/z/tEYKIq
>From gcc-bugs-return-630161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:06:21 2019
Return-Path: <gcc-bugs-return-630161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92196 invoked by alias); 22 Jan 2019 08:06: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 92055 invoked by uid 48); 22 Jan 2019 08:06:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88969] ICE in build_op_delete_call, at cp/call.c:6509
Date: Tue, 22 Jan 2019 08:06: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88969-4-FceXZaDjY7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88969-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: 2019-01/txt/msg02970.txt.bz2
Content-length: 978

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2019-01-22
                 CC|                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Can't reproduce with current trunk, I only see:

g++ pr88969.cpp -c -std=c++2a -fchecking=1
pr88969.cpp:13:21: error: expected initializer at end of input
   13 |   void delete_B(B *b)
      |                     ^
pr88969.cpp:13:21: error: expected â€˜}â€™ at end of input
pr88969.cpp:8:28: note: to match this â€˜{â€™
    8 | namespace delete_selection {
      |                            ^
>From gcc-bugs-return-630162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:09:27 2019
Return-Path: <gcc-bugs-return-630162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104708 invoked by alias); 22 Jan 2019 08:09:25 -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 104628 invoked by uid 48); 22 Jan 2019 08:09:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88968] [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 08:09: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: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88968-4-TtuGUaS8Fd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg02971.txt.bz2
Content-length: 961

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
   Target Milestone|---                         |8.3
     Ever confirmed|0                           |1
      Known to fail|                            |8.2.0, 9.0

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, it's rejected with GCC 7.4.0:
pr88968.c: In function â€˜ypâ€™:
pr88968.c:9:9: error: cannot take address of bit-field â€˜hqâ€™
 #pragma omp atomic
         ^~~

so started with r250929.
>From gcc-bugs-return-630163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:11:30 2019
Return-Path: <gcc-bugs-return-630163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106876 invoked by alias); 22 Jan 2019 08:11:29 -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 106819 invoked by uid 48); 22 Jan 2019 08:11:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88966] Indirect stringification of "linux" produces "1"
Date: Tue, 22 Jan 2019 08:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: bug_status cf_reconfirmed_on cc component everconfirmed
Message-ID: <bug-88966-4-gQbqSNcPzg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88966-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: 2019-01/txt/msg02972.txt.bz2
Content-length: 668

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |marxin at gcc dot gnu.org
          Component|c                           |preprocessor
     Ever confirmed|0                           |1

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, happens will all releases I have (4.8.0+).
>From gcc-bugs-return-630164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:13:29 2019
Return-Path: <gcc-bugs-return-630164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109212 invoked by alias); 22 Jan 2019 08:13:28 -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 109139 invoked by uid 48); 22 Jan 2019 08:13:24 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 08:13: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88965-4-EzwvqZhkFF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg02973.txt.bz2
Content-length: 682

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2019-01-22
                 CC|                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Can you please provide full command line you use for the compilation?
I can't reproduce for the snippet for a cross-compiler.
>From gcc-bugs-return-630165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:14:19 2019
Return-Path: <gcc-bugs-return-630165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112698 invoked by alias); 22 Jan 2019 08:14:18 -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 112039 invoked by uid 48); 22 Jan 2019 08:14:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 08:14: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88965-4-pHX2zBlipd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg02974.txt.bz2
Content-length: 578

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45488
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45488&action=edit
gcc9-pr88965.patch

Untested fix.
>From gcc-bugs-return-630166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:17:12 2019
Return-Path: <gcc-bugs-return-630166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38518 invoked by alias); 22 Jan 2019 08:17:12 -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 38441 invoked by uid 48); 22 Jan 2019 08:17:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 08:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-88964-4-v1T3ht91Ju@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg02975.txt.bz2
Content-length: 710

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |amker at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
   Target Milestone|---                         |8.3
     Ever confirmed|0                           |1

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Anyway, started with r255472.
>From gcc-bugs-return-630167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:18:22 2019
Return-Path: <gcc-bugs-return-630167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41210 invoked by alias); 22 Jan 2019 08:18:22 -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 41159 invoked by uid 48); 22 Jan 2019 08:18:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88958] ICE in walk_aliased_vdefs_1, at tree-ssa-alias.c:2887
Date: Tue, 22 Jan 2019 08:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88958-4-SbghVROBZt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88958-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: 2019-01/txt/msg02976.txt.bz2
Content-length: 558

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |ibuclaw at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1
>From gcc-bugs-return-630168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:19:03 2019
Return-Path: <gcc-bugs-return-630168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42360 invoked by alias); 22 Jan 2019 08:19:02 -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 42236 invoked by uid 48); 22 Jan 2019 08:18:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88957] ICE: Segmentation fault in tree_could_trap_p, at tree-eh.c:2672
Date: Tue, 22 Jan 2019 08:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88957-4-xYQ5Yt0YQi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88957-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: 2019-01/txt/msg02977.txt.bz2
Content-length: 558

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |ibuclaw at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1
>From gcc-bugs-return-630169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:21:42 2019
Return-Path: <gcc-bugs-return-630169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45366 invoked by alias); 22 Jan 2019 08:21:41 -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 45323 invoked by uid 48); 22 Jan 2019 08:21:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88956] [9 Regression] ICE: Floating point exception
Date: Tue, 22 Jan 2019 08:21: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cc cf_known_to_work assigned_to cf_known_to_fail
Message-ID: <bug-88956-4-SNAAPQ9con@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88956-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: 2019-01/txt/msg02978.txt.bz2
Content-length: 712

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
             Status|NEW                         |ASSIGNED
                 CC|                            |marxin at gcc dot gnu.org
      Known to work|                            |8.2.0
           Assignee|unassigned at gcc dot gnu.org      |msebor at gcc dot gnu.org
      Known to fail|                            |9.0

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Started with r262522.
>From gcc-bugs-return-630170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:35:38 2019
Return-Path: <gcc-bugs-return-630170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78199 invoked by alias); 22 Jan 2019 08:35: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 78077 invoked by uid 55); 22 Jan 2019 08:35:34 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 08:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-WFKhDZNt1A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg02979.txt.bz2
Content-length: 1323

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

--- Comment #21 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, elrodc at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #19 from Chris Elrod <elrodc at gmail dot com> ---
> To add a little more:
> I used inline asm for direct access to the rsqrt instruction "vrsqrt14ps" in
> Julia. Without adding a Newton step, the answers are wrong beyond just a couple
> significant digits.
> With the Newton step, the answers are correct.
> 
> My point is that LLVM-compiled code (Clang/Flang/ispc) are definitely adding
> the Newton step. They get the correct answer.
> 
> That leaves my best guess for the performance difference as owing to the masked
> "vrsqrt14ps" that gcc is using:
> 
>         vcmpps  $4, %zmm0, %zmm5, %k1
>         vrsqrt14ps      %zmm0, %zmm1{%k1}{z}
> 
> Is there any way for me to test that idea?
> Edit the asm to remove the vcmppss and mask, compile the asm with gcc, and
> benchmark it?

Usually it's easiest to compile to assembler with GCC (-S) and test
this kind of theories by editing the GCC generated assembly and
then benchmark that.  Just use the assembler as input to the
gfortran compile command instead of the .f for linking the program.
>From gcc-bugs-return-630171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:41:16 2019
Return-Path: <gcc-bugs-return-630171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92515 invoked by alias); 22 Jan 2019 08:41:16 -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 90703 invoked by uid 48); 22 Jan 2019 08:41:12 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88966] Indirect stringification of "linux" produces "1"
Date: Tue, 22 Jan 2019 08:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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:
Message-ID: <bug-88966-4-DNrP1voHnH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88966-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: 2019-01/txt/msg02980.txt.bz2
Content-length: 219

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The same reason why:
#define mymacro 1

str(mymacro)
stringify(mymacro)

Gives different results.
>From gcc-bugs-return-630172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:53:08 2019
Return-Path: <gcc-bugs-return-630172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120768 invoked by alias); 22 Jan 2019 08:53:06 -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 120658 invoked by uid 48); 22 Jan 2019 08:53:01 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88969] ICE in build_op_delete_call, at cp/call.c:6509
Date: Tue, 22 Jan 2019 08:53: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-88969-4-y06lXixsK1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88969-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: 2019-01/txt/msg02981.txt.bz2
Content-length: 689

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

--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> ---
I get what you see when I modify the testcase from comment 0 the following way:

--- mi9qy2yt.cpp        2019-01-22 15:48:53.473604944 +0700
+++ r9d6mwt2.cpp        2019-01-22 15:46:45.567008369 +0700
@@ -1,3 +1,4 @@
+
 namespace std {
   struct destroying_delete_t {
     struct __construct { explicit __construct() = default; };
@@ -9,5 +10,5 @@
     void operator delete(void*) = delete;
     void operator delete(B *, std::destroying_delete_t) = delete;
   };
-  void delete_B(B *b) { delete b; }
-}
+  void delete_B(B *b)
+


Looks like a copy-paste error?
>From gcc-bugs-return-630173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:53:44 2019
Return-Path: <gcc-bugs-return-630173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121879 invoked by alias); 22 Jan 2019 08:53:43 -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 121828 invoked by uid 48); 22 Jan 2019 08:53:38 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88969] ICE in build_op_delete_call, at cp/call.c:6509
Date: Tue, 22 Jan 2019 08:53: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-88969-4-LmPIUqgEWX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88969-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: 2019-01/txt/msg02982.txt.bz2
Content-length: 4037

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

--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
--- mi9qy2yt.cpp        2019-01-22 15:51:33.410845340 +0700
+++ tbfkgb7c.cpp        2019-01-22 15:51:28.620898102 +0700
@@ -7,7 +7,7 @@
 namespace delete_selection {
   struct B {
     void operator delete(void*) = delete;
-    void operator delete(B *, std::destroying_delete_t) = delete;
+    void operator delete(void *, std::destroying_delete_t) = delete;
   };
   void delete_B(B *b) { delete b; }
 }

% g++-9.0.0-alpha20190120 -c tbfkgb7c.cpp
tbfkgb7c.cpp:10:62: internal compiler error: Segmentation fault
   10 |     void operator delete(void *, std::destroying_delete_t) = delete;
      |                                                              ^~~~~~
0xf9cb6f crash_signal
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/toplev.c:326
0xa5ad2f tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.h:3298
0xa5ad2f comptypes(tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/typeck.c:1465
0x926cc7 coerce_delete_type(tree_node*, unsigned int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl2.c:1776
0x8ff2ba grok_op_properties(tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl.c:13472
0x90c3ac grokfndecl
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl.c:9034
0x916b60 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*,
decl_context, int, tree_node**)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl.c:12424
0x92a54e grokfield(cp_declarator const*, cp_decl_specifier_seq*, tree_node*,
bool, tree_node*, tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl2.c:814
0x9c13cf cp_parser_member_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:24656
0x999f9f cp_parser_member_specification_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:24129
0x999f9f cp_parser_class_specifier_1
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:23273
0x99bc98 cp_parser_class_specifier
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:23535
0x99bc98 cp_parser_type_specifier
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:17356
0x99cc50 cp_parser_decl_specifier_seq
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:14049
0x99d424 cp_parser_simple_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13354
0x9c2cdd cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13173
0x9c389c cp_parser_declaration_seq_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13049
0x9c389c cp_parser_namespace_body
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:19252
0x9c389c cp_parser_namespace_definition
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:19230
0x9c2df0 cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13153
>From gcc-bugs-return-630174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:55:24 2019
Return-Path: <gcc-bugs-return-630174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123938 invoked by alias); 22 Jan 2019 08:55:23 -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 123877 invoked by uid 48); 22 Jan 2019 08:55:17 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35476] Accepts invalid: USE/host association of generics with same specifics
Date: Tue, 22 Jan 2019 08:55: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.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-35476-4-O9Svqg5G61@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35476-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35476-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: 2019-01/txt/msg02983.txt.bz2
Content-length: 509

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #9 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
This is still present and not caught by gfortran, according to the interp from
J3 the code is invalid.
>From gcc-bugs-return-630175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:58:20 2019
Return-Path: <gcc-bugs-return-630175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129900 invoked by alias); 22 Jan 2019 08:58:17 -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 129813 invoked by uid 48); 22 Jan 2019 08:58:14 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88924] [GCOV] Wrong frequencies when there is complicated if expressions in gcov
Date: Tue, 22 Jan 2019 08:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88924-4-0uRrmRppNW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88924-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88924-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: 2019-01/txt/msg02984.txt.bz2
Content-length: 610

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P5
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, it's related to some subexpression folding. Thus low priority to
fix.
>From gcc-bugs-return-630176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 08:59:43 2019
Return-Path: <gcc-bugs-return-630176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3423 invoked by alias); 22 Jan 2019 08:59:43 -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 3285 invoked by uid 48); 22 Jan 2019 08:59:39 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35779] error pointer wrong in PARAMETER
Date: Tue, 22 Jan 2019 08:59: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.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-35779-4-Cno0Ikm1Ul@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35779-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: 2019-01/txt/msg02985.txt.bz2
Content-length: 429

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #13 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Still present in trunk.
>From gcc-bugs-return-630177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:05:26 2019
Return-Path: <gcc-bugs-return-630177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21410 invoked by alias); 22 Jan 2019 09:05:25 -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 21323 invoked by uid 48); 22 Jan 2019 09:05:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88913] [GCOV] Wrong frequencies when a global variable is in a while expression in gcov
Date: Tue, 22 Jan 2019 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-88913-4-prI06gx3ls@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88913-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: 2019-01/txt/msg02986.txt.bz2
Content-length: 453

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Fixed on trunk in r247374.
>From gcc-bugs-return-630178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:07:34 2019
Return-Path: <gcc-bugs-return-630178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26390 invoked by alias); 22 Jan 2019 09:07:34 -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 25905 invoked by uid 48); 22 Jan 2019 09:07:30 -0000
From: "yangyibiao at nju dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88913] [GCOV] Wrong frequencies when a global variable is in a while expression in gcov
Date: Tue, 22 Jan 2019 09:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yangyibiao at nju dot edu.cn
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-88913-4-IaMjxyeoX0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88913-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: 2019-01/txt/msg02987.txt.bz2
Content-length: 207

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

--- Comment #2 from Yibiao Yang <yangyibiao at nju dot edu.cn> ---
(In reply to Martin LiÅ¡ka from comment #1)
> Fixed on trunk in r247374.

Thanks.
>From gcc-bugs-return-630179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:07:46 2019
Return-Path: <gcc-bugs-return-630179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27665 invoked by alias); 22 Jan 2019 09:07:45 -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 27060 invoked by uid 48); 22 Jan 2019 09:07:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88969] ICE in build_op_delete_call, at cp/call.c:6509
Date: Tue, 22 Jan 2019 09:07: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: bug_status cc
Message-ID: <bug-88969-4-hYszex51Lz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88969-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: 2019-01/txt/msg02988.txt.bz2
Content-length: 473

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |jason at gcc dot gnu.org

--- Comment #4 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, started with r266053.
>From gcc-bugs-return-630183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:11:09 2019
Return-Path: <gcc-bugs-return-630183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33713 invoked by alias); 22 Jan 2019 09:11:09 -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 33264 invoked by uid 55); 22 Jan 2019 09:11:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49429] [4.7 Regression] dse.c change (r175063) causes execution failures
Date: Tue, 22 Jan 2019 09:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49429-4-KKmHnN1GQJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49429-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: 2019-01/txt/msg02990.txt.bz2
Content-length: 819

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

--- Comment #21 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:10:25 2019
New Revision: 268138

URL: https://gcc.gnu.org/viewcvs?rev=268138&root=gcc&view=rev
Log:
        PR rtl-optimization/49429
        PR target/49454
        PR rtl-optimization/86334
        PR target/88906
        * expr.c (emit_block_move_hints): Move marking of MEM_EXPRs
        addressable from here...
        (emit_block_op_via_libcall): ... to here.

        * gcc.target/i386/pr86334.c: New test.
        * gcc.target/i386/pr88906.c: New test.

Added:
    trunk/gcc/testsuite/gcc.target/i386/pr86334.c
    trunk/gcc/testsuite/gcc.target/i386/pr88906.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/expr.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:11:08 2019
Return-Path: <gcc-bugs-return-630181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33442 invoked by alias); 22 Jan 2019 09:11:07 -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 33229 invoked by uid 55); 22 Jan 2019 09:11:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86334] wrong code with -march=athlon -mmemcpy-strategy=libcall:-1:noalign
Date: Tue, 22 Jan 2019 09:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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-86334-4-QvvMA1Rhfv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86334-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86334-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: 2019-01/txt/msg02991.txt.bz2
Content-length: 818

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:10:25 2019
New Revision: 268138

URL: https://gcc.gnu.org/viewcvs?rev=268138&root=gcc&view=rev
Log:
        PR rtl-optimization/49429
        PR target/49454
        PR rtl-optimization/86334
        PR target/88906
        * expr.c (emit_block_move_hints): Move marking of MEM_EXPRs
        addressable from here...
        (emit_block_op_via_libcall): ... to here.

        * gcc.target/i386/pr86334.c: New test.
        * gcc.target/i386/pr88906.c: New test.

Added:
    trunk/gcc/testsuite/gcc.target/i386/pr86334.c
    trunk/gcc/testsuite/gcc.target/i386/pr88906.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/expr.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:11:08 2019
Return-Path: <gcc-bugs-return-630182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33486 invoked by alias); 22 Jan 2019 09:11:07 -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 33220 invoked by uid 55); 22 Jan 2019 09:11:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Tue, 22 Jan 2019 09:11: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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:
Message-ID: <bug-88906-4-YuLcBFOu6B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg02992.txt.bz2
Content-length: 818

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:10:25 2019
New Revision: 268138

URL: https://gcc.gnu.org/viewcvs?rev=268138&root=gcc&view=rev
Log:
        PR rtl-optimization/49429
        PR target/49454
        PR rtl-optimization/86334
        PR target/88906
        * expr.c (emit_block_move_hints): Move marking of MEM_EXPRs
        addressable from here...
        (emit_block_op_via_libcall): ... to here.

        * gcc.target/i386/pr86334.c: New test.
        * gcc.target/i386/pr88906.c: New test.

Added:
    trunk/gcc/testsuite/gcc.target/i386/pr86334.c
    trunk/gcc/testsuite/gcc.target/i386/pr88906.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/expr.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:11:55 2019
Return-Path: <gcc-bugs-return-630184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36638 invoked by alias); 22 Jan 2019 09:11:54 -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 36587 invoked by uid 48); 22 Jan 2019 09:11:51 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35718] deallocating non-allocated pointer target does not fail
Date: Tue, 22 Jan 2019 09:11: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.4.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-35718-4-NGSnNCFkGA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35718-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: 2019-01/txt/msg02993.txt.bz2
Content-length: 153

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

--- Comment #6 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Still present in trunk.
>From gcc-bugs-return-630180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:11:07 2019
Return-Path: <gcc-bugs-return-630180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33414 invoked by alias); 22 Jan 2019 09:11:06 -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 33222 invoked by uid 55); 22 Jan 2019 09:11:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49454] [4.7 Regression] /usr/include/libio.h:336:3: internal compiler error: Segmentation fault
Date: Tue, 22 Jan 2019 09:11: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: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49454-4-pvYMYOGg7J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49454-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49454-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: 2019-01/txt/msg02989.txt.bz2
Content-length: 818

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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:10:25 2019
New Revision: 268138

URL: https://gcc.gnu.org/viewcvs?rev=268138&root=gcc&view=rev
Log:
        PR rtl-optimization/49429
        PR target/49454
        PR rtl-optimization/86334
        PR target/88906
        * expr.c (emit_block_move_hints): Move marking of MEM_EXPRs
        addressable from here...
        (emit_block_op_via_libcall): ... to here.

        * gcc.target/i386/pr86334.c: New test.
        * gcc.target/i386/pr88906.c: New test.

Added:
    trunk/gcc/testsuite/gcc.target/i386/pr86334.c
    trunk/gcc/testsuite/gcc.target/i386/pr88906.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/expr.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:12:13 2019
Return-Path: <gcc-bugs-return-630185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37549 invoked by alias); 22 Jan 2019 09:12:12 -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 37485 invoked by uid 55); 22 Jan 2019 09:12:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88905] [8/9 Regression] ICE: in decompose, at rtl.h:2253 with -mabm and __builtin_popcountll
Date: Tue, 22 Jan 2019 09:12: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88905-4-v5WN22P3Xd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88905-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: 2019-01/txt/msg02994.txt.bz2
Content-length: 748

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:11:35 2019
New Revision: 268139

URL: https://gcc.gnu.org/viewcvs?rev=268139&root=gcc&view=rev
Log:
        PR target/88905
        * optabs.c (add_equal_note): Add op0_mode argument, use it instead of
        GET_MODE (op0).
        (expand_binop_directly, expand_doubleword_clz,
        expand_doubleword_popcount, expand_ctz, expand_ffs,
        expand_unop_direct, maybe_emit_unop_insn): Adjust callers.

        * gcc.dg/pr88905.c: New test.

Added:
    trunk/gcc/testsuite/gcc.dg/pr88905.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/optabs.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:13:10 2019
Return-Path: <gcc-bugs-return-630186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39128 invoked by alias); 22 Jan 2019 09:13:09 -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 39050 invoked by uid 55); 22 Jan 2019 09:13:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88904] [9 Regression] Basic block incorrectly skipped in jump threading.
Date: Tue, 22 Jan 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88904-4-lHhMieRO7J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88904-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: 2019-01/txt/msg02995.txt.bz2
Content-length: 634

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:12:31 2019
New Revision: 268140

URL: https://gcc.gnu.org/viewcvs?rev=268140&root=gcc&view=rev
Log:
        PR rtl-optimization/88904
        * cfgcleanup.c (thread_jump): Verify cond2 doesn't mention
        any nonequal registers before processing BB_END (b).

        * gcc.c-torture/execute/pr88904.c: New test.

Added:
    trunk/gcc/testsuite/gcc.c-torture/execute/pr88904.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cfgcleanup.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:13:43 2019
Return-Path: <gcc-bugs-return-630187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40764 invoked by alias); 22 Jan 2019 09:13:42 -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 39972 invoked by uid 48); 22 Jan 2019 09:13:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88905] [8 Regression] ICE: in decompose, at rtl.h:2253 with -mabm and __builtin_popcountll
Date: Tue, 22 Jan 2019 09:13: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88905-4-6ZTcvtRDmB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88905-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: 2019-01/txt/msg02996.txt.bz2
Content-length: 610

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[8/9 Regression] ICE: in    |[8 Regression] ICE: in
                   |decompose, at rtl.h:2253    |decompose, at rtl.h:2253
                   |with -mabm and              |with -mabm and
                   |__builtin_popcountll        |__builtin_popcountll

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-630188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:15:51 2019
Return-Path: <gcc-bugs-return-630188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54422 invoked by alias); 22 Jan 2019 09:15: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 54341 invoked by uid 48); 22 Jan 2019 09:15:45 -0000
From: "christopher.leonard at abaco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 09:15: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christopher.leonard at abaco dot com
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:
Message-ID: <bug-88952-4-DXNpkUzK4h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg02997.txt.bz2
Content-length: 345

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

--- Comment #5 from Christopher Leonard <christopher.leonard at abaco dot com> ---
Is the order at least consistant with x86-32? i.e. if you give a 64-bit input
operand to inline assembly the order is hi:lo? I'm worried this is a bizarre
convention imposed on high endian architectures.
>From gcc-bugs-return-630189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:17:53 2019
Return-Path: <gcc-bugs-return-630189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56683 invoked by alias); 22 Jan 2019 09:17:53 -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 56587 invoked by uid 48); 22 Jan 2019 09:17:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 09:17: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: bug_status cc blocked everconfirmed
Message-ID: <bug-88963-4-fHnEb818EN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg02998.txt.bz2
Content-length: 5399

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |jakub at gcc dot gnu.org
             Blocks|                            |88670
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  The reason is that vector lowering only lowers the arithmetic
but leaves the loads and stores alone:

   _1 = *b_5(D);
   _2 = *c_6(D);
-  _3 = _1 + _2;
+  _9 = BIT_FIELD_REF <_1, 128, 0>;
+  _10 = BIT_FIELD_REF <_2, 128, 0>;
+  _11 = _9 + _10;
+  _12 = BIT_FIELD_REF <_1, 128, 128>;
+  _13 = BIT_FIELD_REF <_2, 128, 128>;
+  _14 = _12 + _13;
+  _15 = BIT_FIELD_REF <_1, 128, 256>;
+  _16 = BIT_FIELD_REF <_2, 128, 256>;
+  _17 = _15 + _16;
+  _18 = BIT_FIELD_REF <_1, 128, 384>;
+  _19 = BIT_FIELD_REF <_2, 128, 384>;
+  _20 = _18 + _19;
+  _3 = {_11, _14, _17, _20};
   *a_7(D) = _3;

there's some hack^Wcode in tree-ssa-forwprop.c to deal with similar cases
using {REAL,IMAG}PART_EXPR and COMPLEX_EXPR, splitting feeding/destination
memory accesses.  The same trick is missing for vector loads/stores.

OTOH it would be more reasonable for vector lowering to split the loads.
It's not so difficult to do - the main "issue" would be making sure
the wide vector load goes away (or maybe that's even a secondary issue
that could be ignored).

With just the loads handled code generation improves to

test:
.LFB0:
        .cfi_startproc
        pushq   %rbp
        .cfi_def_cfa_offset 16
        .cfi_offset 6, -16
        movq    %rsp, %rbp
        .cfi_def_cfa_register 6
        andq    $-64, %rsp
        subq    $8, %rsp
        movdqa  (%rsi), %xmm3
        movdqa  16(%rsi), %xmm2
        movdqa  32(%rsi), %xmm1
        movdqa  48(%rsi), %xmm0
        paddd   (%rdx), %xmm3
        paddd   16(%rdx), %xmm2
        paddd   32(%rdx), %xmm1
        paddd   48(%rdx), %xmm0
        movaps  %xmm3, (%rdi)
        movaps  %xmm2, 16(%rdi)
        movaps  %xmm1, 32(%rdi)
        movaps  %xmm0, 48(%rdi)
        leave
        ret
        .cfi_endproc

for SSE2 and

test:
.LFB0:
        .cfi_startproc
        pushq   %rbp
        .cfi_def_cfa_offset 16
        .cfi_offset 6, -16
        movq    %rsp, %rbp
        .cfi_def_cfa_register 6
        andq    $-64, %rsp
        subq    $8, %rsp
        vmovdqa (%rsi), %ymm3
        vpaddd  (%rdx), %ymm3, %ymm0
        vmovdqa %xmm0, %xmm2
        vmovdqa %ymm0, -120(%rsp)
        vmovdqa 32(%rsi), %ymm0
        vmovdqa -104(%rsp), %xmm4
        vpaddd  32(%rdx), %ymm0, %ymm0
        vmovaps %xmm2, (%rdi)
        vmovdqa %ymm0, -88(%rsp)
        vmovdqa -72(%rsp), %xmm5
        vmovaps %xmm4, 16(%rdi)
        vmovaps %xmm0, 32(%rdi)
        vmovaps %xmm0, 32(%rdi)
        vmovaps %xmm5, 48(%rdi)
        vzeroupper
        leave
        .cfi_def_cfa 7, 8
        ret

for skylake.  Not sure why we spill anything with the above, with the SSE
code we manage to elide the spills (but not the stack reservation).  I
guess we need to handle the stores as well.

The odd thing is that if I simply do

  _12 = BIT_FIELD_REF <*b_5(D), 256, 256>;
  _9 = BIT_FIELD_REF <*b_5(D), 256, 0>;
  _13 = BIT_FIELD_REF <*c_6(D), 256, 256>;
  _10 = BIT_FIELD_REF <*c_6(D), 256, 0>;
  _11 = _9 + _10;
  _14 = _12 + _13;
  BIT_FIELD_REF <*a_7(D), 256, 0> = _11;
  BIT_FIELD_REF <*a_7(D), 256, 256> = _14;

code-generation is even worse:

        vmovdqa (%rsi), %ymm0
        vmovdqa 32(%rsi), %ymm2
        vpaddd  (%rdx), %ymm0, %ymm3
        vpaddd  32(%rdx), %ymm2, %ymm1
        vmovdqa %ymm3, -64(%rsp)
        movq    -56(%rsp), %rax
        vmovdqa %ymm1, -32(%rsp)
        movq    %rax, 8(%rdi)
        movq    -48(%rsp), %rax
        vmovdqa -64(%rsp), %xmm0
        movq    %rax, 16(%rdi)
        movq    -40(%rsp), %rax
        vmovq   %xmm0, (%rdi)
        movq    %rax, 24(%rdi)
        movq    -24(%rsp), %rax
        vmovdqa -32(%rsp), %xmm0
        movq    %rax, 40(%rdi)
        movq    -16(%rsp), %rax
        vmovq   %xmm0, 32(%rdi)
        movq    %rax, 48(%rdi)
        movq    -8(%rsp), %rax
        movq    %rax, 56(%rdi)
        vzeroupper
        leave
        .cfi_def_cfa 7, 8
        ret

the stores expand to

;; BIT_FIELD_REF <*a_7(D), 256, 0> = _11;

(insn 14 13 15 (set (mem/j:DI (reg/v/f:DI 88 [ a ]) [1 *a_7(D)+0 S8 A256])
        (subreg:DI (reg:V8SI 84 [ _11 ]) 0)) "t.c":6:6 -1
     (nil))

(insn 15 14 16 (set (mem/j:DI (plus:DI (reg/v/f:DI 88 [ a ])
                (const_int 8 [0x8])) [1 *a_7(D)+8 S8 A64])
        (subreg:DI (reg:V8SI 84 [ _11 ]) 8)) "t.c":6:6 -1
     (nil))

(insn 16 15 17 (set (mem/j:DI (plus:DI (reg/v/f:DI 88 [ a ])
                (const_int 16 [0x10])) [1 *a_7(D)+16 S8 A128])
        (subreg:DI (reg:V8SI 84 [ _11 ]) 16)) "t.c":6:6 -1
     (nil))

(insn 17 16 0 (set (mem/j:DI (plus:DI (reg/v/f:DI 88 [ a ])
                (const_int 24 [0x18])) [1 *a_7(D)+24 S8 A64])
        (subreg:DI (reg:V8SI 84 [ _11 ]) 24)) "t.c":6:6 -1
     (nil))

for whatever reason.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
[Bug 88670] [meta-bug] generic vector extension issues
>From gcc-bugs-return-630190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:18:29 2019
Return-Path: <gcc-bugs-return-630190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65366 invoked by alias); 22 Jan 2019 09:18:29 -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 65202 invoked by uid 48); 22 Jan 2019 09:18:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 09:18: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: attachments.created
Message-ID: <bug-88963-4-0Cz6GJdbmh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg02999.txt.bz2
Content-length: 273

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45489
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45489&action=edit
untested patch

forwprop patch I was playing with.
>From gcc-bugs-return-630191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:19:58 2019
Return-Path: <gcc-bugs-return-630191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83857 invoked by alias); 22 Jan 2019 09:19:58 -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 81670 invoked by uid 48); 22 Jan 2019 09:19:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 09:19: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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:
Message-ID: <bug-88963-4-1nvIZAus10@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03000.txt.bz2
Content-length: 446

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, I've noticed that already when working on __builtin_convertvector, we
don't really do much TER for the oversized vector SSA_NAMEs and force them into
stack all the time.  Wonder if we couldn't do kind of SRA for these vectors
after generic vector lowering to split them into multiple unrelated SSA_NAMEs
if possible.
>From gcc-bugs-return-630192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:20:45 2019
Return-Path: <gcc-bugs-return-630192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85582 invoked by alias); 22 Jan 2019 09:20:43 -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 85392 invoked by uid 48); 22 Jan 2019 09:20:39 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88951] [9 Regression] No fpermissive offerred on 'error: jump to case label'
Date: Tue, 22 Jan 2019 09:20: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88951-4-zmUmkQY18a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88951-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: 2019-01/txt/msg03001.txt.bz2
Content-length: 568

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

--- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> ---
The rationale for the change is here:
https://gcc.gnu.org/ml/gcc-patches/2018-08/msg00623.html I my experience,
accepting such kind of code is really dangerous, because -fpermissive isn't
fine grained thus in some cases users want to pass it to allow for other *safe*
legacy constructs. That said, clarified that I vote NO, NO based on real, hard,
experience, it's the front-end maintainers call, reverting the change would be
trivial.
>From gcc-bugs-return-630193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:21:09 2019
Return-Path: <gcc-bugs-return-630193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86648 invoked by alias); 22 Jan 2019 09:21:08 -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 86594 invoked by uid 48); 22 Jan 2019 09:21:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 09:21: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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:
Message-ID: <bug-88952-4-v4DSlX4moT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg03002.txt.bz2
Content-length: 501

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Christopher Leonard from comment #5)
> Is the order at least consistant with x86-32? i.e. if you give a 64-bit
> input operand to inline assembly the order is hi:lo? I'm worried this is a
> bizarre convention imposed on high endian architectures.

Yes the order is always hi:lo (reg:reg+1) on all targets I know of; endianness
only matters when it comes to memory.
>From gcc-bugs-return-630194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:23:28 2019
Return-Path: <gcc-bugs-return-630194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116498 invoked by alias); 22 Jan 2019 09:23:27 -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 116400 invoked by uid 48); 22 Jan 2019 09:23:23 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 09:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-SaI9un9cNu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03003.txt.bz2
Content-length: 2591

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

--- Comment #22 from Chris Elrod <elrodc at gmail dot com> ---
Okay. I did that, and the time went from about 4.25 microseconds down to 4.0
microseconds. So that is an improvement, but accounts for only a small part of
the difference with the LLVM-compilers.

-O3 -fno-math-errno

was about 3.5 microseconds, so -funsafe-math-optimizations still results in a
regression in this code.

3.5 microseconds is roughly as fast as you can get with vsqrt and div.

My best guess now is that gcc does a lot more to improve the accuracy of vsqrt.
If I understand correctly, these are all the involved instructions:

        vmovaps .LC2(%rip), %zmm7
        vmovaps .LC3(%rip), %zmm6
        # for loop begins
        vrsqrt14ps      %zmm1, %zmm2 # comparison and mask removed
        vmulps  %zmm1, %zmm2, %zmm0
        vmulps  %zmm2, %zmm0, %zmm1
        vmulps  %zmm6, %zmm0, %zmm0
        vaddps  %zmm7, %zmm1, %zmm1
        vmulps  %zmm0, %zmm1, %zmm1
        vrcp14ps        %zmm1, %zmm0
        vmulps  %zmm1, %zmm0, %zmm1
        vmulps  %zmm1, %zmm0, %zmm1
        vaddps  %zmm0, %zmm0, %zmm0
        vsubps  %zmm1, %zmm0, %zmm0
        vfnmadd213ps    (%r10,%rax), %zmm0, %zmm2

If I understand this correctly:

zmm2 =(approx) 1 / sqrt(zmm1)
zmm0 = zmm1 * zmm2 = (approx) sqrt(zmm1)
zmm1 = zmm0 * zmm2 = (approx) 1
zmm0 = zmm6 * zmm0 = (approx) constant6 * sqrt(zmm1)
zmm1 = zmm7 * zmm1 = (approx) constant7
zmm1 = zmm0 * zmm1 = (approx) constant6 * constant6 * sqrt(zmm1)
zmm0 = (approx) 1 / zmm1 = (approx) 1 / sqrt(zmm1) * 1 / (constant6 *
constant7)
zmm1 = zmm1 * zmm0 = (approx) 1
zmm1 = zmm1 * zmm0 = (approx) 1 / sqrt(zmm1) * 1 / (constant6 * constant7)
zmm0 = 2 * zmm0 = (approx) 2 / sqrt(zmm1) * 2 / (constant6 * constant7)
zmm0 = zmm1 - zmm0 = (approx) -1 / sqrt(zmm1) * 1 / (constant6 * constant7)

which implies that constant6 * constant6 = approximately -1?


LLVM seems to do a much simpler / briefer update of the output of vrsqrt.

When I implemented a vrsqrt intrinsic in a Julia library, I just looked at
Wikipedia and did (roughly):

constant1 = -0.5
constant2 = 1.5

zmm2 = (approx) 1 / sqrt(zmm1)
zmm3 = constant * zmm1
zmm1 = zmm2 * zmm2
zmm3 = zmm3 * zmm1 + constant2
zmm2 = zmm2 * zmm3


I am not a numerical analyst, so I can't comment on relative validities or
accuracies of these approaches.
I also don't know what LLVM 7+ does. LLVM 6 doesn't use vrsqrt.

I would be interesting in reading explanations or discussions, if any are
available.
>From gcc-bugs-return-630195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:29:10 2019
Return-Path: <gcc-bugs-return-630195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3620 invoked by alias); 22 Jan 2019 09:29:08 -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 754 invoked by uid 48); 22 Jan 2019 09:29:03 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37222] [OOP] Checks when overriding type-bound procedures are incomplete
Date: Tue, 22 Jan 2019 09:29: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: unknown
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-37222-4-Q2ybXtPhS4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37222-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37222-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: 2019-01/txt/msg03004.txt.bz2
Content-length: 528

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #4 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
As Janus commented there is just one left-over (already fixed in the past six
years?). So what is really left to do here?
>From gcc-bugs-return-630196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:32:53 2019
Return-Path: <gcc-bugs-return-630196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13407 invoked by alias); 22 Jan 2019 09:32:53 -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 13332 invoked by uid 48); 22 Jan 2019 09:32:49 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37398] Statement functions mask missing PURE procedures.
Date: Tue, 22 Jan 2019 09: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.4.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-37398-4-qDqXmsXoSX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37398-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: 2019-01/txt/msg03005.txt.bz2
Content-length: 502

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #3 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
This correctly gives the expected error messages since at least gfortran 5.4.
Closing as FIXED?
>From gcc-bugs-return-630197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:35:52 2019
Return-Path: <gcc-bugs-return-630197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64961 invoked by alias); 22 Jan 2019 09:35:52 -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 57927 invoked by uid 48); 22 Jan 2019 09:35:47 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38113] on warning/error: skip whitespaces, move position marker to actual variable name
Date: Tue, 22 Jan 2019 09:35: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.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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-38113-4-b3fE4iV1BO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38113-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38113-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: 2019-01/txt/msg03006.txt.bz2
Content-length: 652

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #9 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Here there are some problems that have been fixed, and some new have been
revealed!? To me it is not clear what the exact context is now. Maybe closing
as WORKSFORME, and waiting for someone to open an actual issue with the
alignment of markers?
>From gcc-bugs-return-630198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:36:08 2019
Return-Path: <gcc-bugs-return-630198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85475 invoked by alias); 22 Jan 2019 09:36:07 -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 68940 invoked by uid 55); 22 Jan 2019 09:35:58 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 09:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-SCOrUvTpWO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03007.txt.bz2
Content-length: 3258

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

--- Comment #23 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, elrodc at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #22 from Chris Elrod <elrodc at gmail dot com> ---
> Okay. I did that, and the time went from about 4.25 microseconds down to 4.0
> microseconds. So that is an improvement, but accounts for only a small part of
> the difference with the LLVM-compilers.
> 
> -O3 -fno-math-errno
> 
> was about 3.5 microseconds, so -funsafe-math-optimizations still results in a
> regression in this code.
> 
> 3.5 microseconds is roughly as fast as you can get with vsqrt and div.
> 
> My best guess now is that gcc does a lot more to improve the accuracy of vsqrt.
> If I understand correctly, these are all the involved instructions:
> 
>         vmovaps .LC2(%rip), %zmm7
>         vmovaps .LC3(%rip), %zmm6
>         # for loop begins
>         vrsqrt14ps      %zmm1, %zmm2 # comparison and mask removed
>         vmulps  %zmm1, %zmm2, %zmm0
>         vmulps  %zmm2, %zmm0, %zmm1
>         vmulps  %zmm6, %zmm0, %zmm0
>         vaddps  %zmm7, %zmm1, %zmm1
>         vmulps  %zmm0, %zmm1, %zmm1
>         vrcp14ps        %zmm1, %zmm0
>         vmulps  %zmm1, %zmm0, %zmm1
>         vmulps  %zmm1, %zmm0, %zmm1
>         vaddps  %zmm0, %zmm0, %zmm0
>         vsubps  %zmm1, %zmm0, %zmm0
>         vfnmadd213ps    (%r10,%rax), %zmm0, %zmm2
> 
> If I understand this correctly:
> 
> zmm2 =(approx) 1 / sqrt(zmm1)
> zmm0 = zmm1 * zmm2 = (approx) sqrt(zmm1)
> zmm1 = zmm0 * zmm2 = (approx) 1
> zmm0 = zmm6 * zmm0 = (approx) constant6 * sqrt(zmm1)
> zmm1 = zmm7 * zmm1 = (approx) constant7
> zmm1 = zmm0 * zmm1 = (approx) constant6 * constant6 * sqrt(zmm1)
> zmm0 = (approx) 1 / zmm1 = (approx) 1 / sqrt(zmm1) * 1 / (constant6 *
> constant7)
> zmm1 = zmm1 * zmm0 = (approx) 1
> zmm1 = zmm1 * zmm0 = (approx) 1 / sqrt(zmm1) * 1 / (constant6 * constant7)
> zmm0 = 2 * zmm0 = (approx) 2 / sqrt(zmm1) * 2 / (constant6 * constant7)
> zmm0 = zmm1 - zmm0 = (approx) -1 / sqrt(zmm1) * 1 / (constant6 * constant7)
> 
> which implies that constant6 * constant6 = approximately -1?

GCC implements

 /* sqrt(a)  = -0.5 * a * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0)
    rsqrt(a) = -0.5     * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0) */

which looks similar to what LLVM does.  You can look at the
-fdump-tree-optimized dump to see if there's anything fishy.

> 
> LLVM seems to do a much simpler / briefer update of the output of vrsqrt.
> 
> When I implemented a vrsqrt intrinsic in a Julia library, I just looked at
> Wikipedia and did (roughly):
> 
> constant1 = -0.5
> constant2 = 1.5
> 
> zmm2 = (approx) 1 / sqrt(zmm1)
> zmm3 = constant * zmm1
> zmm1 = zmm2 * zmm2
> zmm3 = zmm3 * zmm1 + constant2
> zmm2 = zmm2 * zmm3
> 
> 
> I am not a numerical analyst, so I can't comment on relative validities or
> accuracies of these approaches.
> I also don't know what LLVM 7+ does. LLVM 6 doesn't use vrsqrt.
> 
> I would be interesting in reading explanations or discussions, if any are
> available.
> 
>
>From gcc-bugs-return-630199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:37:09 2019
Return-Path: <gcc-bugs-return-630199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123083 invoked by alias); 22 Jan 2019 09:37:08 -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 108111 invoked by uid 48); 22 Jan 2019 09:37:03 -0000
From: "nidal.faour at wdc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88422] collect2.exe: fatal error: lto-wrapper returned 1 exit status: file not recognized: file truncated
Date: Tue, 22 Jan 2019 09:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nidal.faour at wdc dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88422-4-3o0RVdDawG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88422-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: 2019-01/txt/msg03008.txt.bz2
Content-length: 1566

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

--- Comment #6 from Nidal Faour <nidal.faour at wdc dot com> ---
Andrew Pinski is right, after chasing this bug with the help of Andrew Burgess
in the file simple-object.c, calling the creat

outfd = creat (dest, 00777);

the creat function wraps the open function but do not pass open mode
and the fix mentioned by Adrew was as follow:

When opening output files for simple-object creation, we must ensure that the
file is opened in binary mode.  Failure to do so causes file corruption, and
LTO failure on Windows targets.

libiberty/ChangeLog:

        PR lto/88422
        * simple-object.c (O_BINARY): Define if not already defined.
        (simple_object_copy_lto_debug_sections): Create file in binary
        mode.
---
 libiberty/ChangeLog       | 7 +++++++
 libiberty/simple-object.c | 6 +++++-
 2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/libiberty/simple-object.c b/libiberty/simple-object.c index
c1f38cee8ee..e061073abd1 100644
--- a/libiberty/simple-object.c
+++ b/libiberty/simple-object.c
@@ -44,6 +44,10 @@ Boston, MA 02110-1301, USA.  */  #define SEEK_SET 0  #endif

+#ifndef O_BINARY
+# define O_BINARY 0
+#endif
+
 #include "simple-object-common.h"

 /* The known object file formats.  */
@@ -349,7 +353,7 @@ simple_object_copy_lto_debug_sections (simple_object_read
*sobj,
       return errmsg;
     }

-  outfd = creat (dest, 00777);
+  outfd = open (dest, O_CREAT|O_WRONLY|O_TRUNC|O_BINARY, 00777);
   if (outfd == -1)
     {
       *err = errno;
--
>From gcc-bugs-return-630200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:38:33 2019
Return-Path: <gcc-bugs-return-630200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71573 invoked by alias); 22 Jan 2019 09:38:32 -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 69022 invoked by uid 48); 22 Jan 2019 09:38:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88919] New test case gcc.dg/vect/pr88903-1.c in r268076 fails
Date: Tue, 22 Jan 2019 09:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-88919-4-IWQSIN8m5z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88919-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: 2019-01/txt/msg03009.txt.bz2
Content-length: 203

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Sandra posted a patch that will probably fix this (out-of-bound shift values).
>From gcc-bugs-return-630202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:39:37 2019
Return-Path: <gcc-bugs-return-630202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82810 invoked by alias); 22 Jan 2019 09:39:36 -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 82706 invoked by uid 48); 22 Jan 2019 09:39:32 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 09:39: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
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-88963-4-Qu0OFRvSR9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03011.txt.bz2
Content-length: 2098

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

Devin Hussey <husseydevin at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |husseydevin at gmail dot com

--- Comment #4 from Devin Hussey <husseydevin at gmail dot com> ---
Strangely, this doesn't seem to affect the ARM or aarch64 backends, although I
am on a December build (specifically Dec 29). 8.2 is also unaffected.

arm-none-eabi-gcc -mfloat-abi=hard -mfpu=neon -march=armv7-a -O3 -S test.c

test:
    vldmia  r1, {d0-d7}
    vldmia  r2, {d24-d31}
    vadd.i32    q8, q0, q12
    vadd.i32    q9, q1, q13
    vadd.i32    q10, q2, q14
    vadd.i32    q11, q3, q15
    vstmia  r0, {d16-d23}
    bx  lr

aarch64-none-eabi-gcc -O3 -S test.c

test:
        ld1     {v16.16b - v19.16b}, [x1]
        ld1     {v4.16b - v7.16b}, [x2]
        add     v0.4s, v16.4s, v4.4s
        add     v1.4s, v17.4s, v5.4s
        add     v2.4s, v18.4s, v6.4s
        add     v3.4s, v19.4s, v7.4s
        st1     {v0.16b - v3.16b}, [x0]
        ret

Amusingly, Clang trunk for ARMv7-a has a similar issue (aarch64 is fine).

test:
        .fnstart
        .save   {r11, lr}
        push    {r11, lr}
        add     r3, r1, #48
        mov     lr, r1
        mov     r12, r2
        vld1.64 {d20, d21}, [r3]
        add     r3, r2, #48
        add     r1, r1, #32
        vld1.32 {d16, d17}, [lr]!
        vld1.32 {d18, d19}, [r12]!
        vadd.i32        q8, q9, q8
        vld1.64 {d22, d23}, [r3]
        vadd.i32        q10, q11, q10
        vld1.64 {d26, d27}, [r1]
        add     r1, r2, #32
        vld1.64 {d28, d29}, [r1]
        add     r1, r0, #48
        vadd.i32        q11, q14, q13
        vld1.64 {d24, d25}, [lr]
        vld1.64 {d18, d19}, [r12]
        vadd.i32        q9, q9, q12
        vst1.64 {d20, d21}, [r1]
        add     r1, r0, #32
        vst1.32 {d16, d17}, [r0]!
        vst1.64 {d22, d23}, [r1]
        vst1.64 {d18, d19}, [r0]
        pop     {r11, pc}
>From gcc-bugs-return-630201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:39:25 2019
Return-Path: <gcc-bugs-return-630201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81991 invoked by alias); 22 Jan 2019 09:39:24 -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 81919 invoked by uid 48); 22 Jan 2019 09:39:20 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88951] [9 Regression] No fpermissive offerred on 'error: jump to case label'
Date: Tue, 22 Jan 2019 09:39: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88951-4-s918nVvOwo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88951-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: 2019-01/txt/msg03010.txt.bz2
Content-length: 401

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

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Also note, further clarifying what I said in the linked messages, that we only
temporarily, for few releases, accepted with -fpermissive such kind of broken
code: before gcc5, -fpermissive suppressed the first error, but then an
additional hard error was emitted anyway.
>From gcc-bugs-return-630203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:41:58 2019
Return-Path: <gcc-bugs-return-630203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122061 invoked by alias); 22 Jan 2019 09:41:57 -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 120274 invoked by uid 48); 22 Jan 2019 09:41:53 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37222] [OOP] Checks when overriding type-bound procedures are incomplete
Date: Tue, 22 Jan 2019 09:41: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: unknown
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-37222-4-2fuRlq8EF7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37222-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37222-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: 2019-01/txt/msg03012.txt.bz2
Content-length: 913

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from janus at gcc dot gnu.org ---
(In reply to JÃ¼rgen Reuter from comment #4)
> As Janus commented there is just one left-over (already fixed in the past
> six years?). So what is really left to do here?

I don't think the left-over is actually fixed (at least the FIXME notes are
still present in interface.c).

In any case, further improvement in this area is rather hard and yields only
little gain, so I think it's reasonable to close this ten-year-old PR that
presents no concrete test case (after all, the FIXMEs are still there for
future reference).
>From gcc-bugs-return-630204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:42:18 2019
Return-Path: <gcc-bugs-return-630204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126261 invoked by alias); 22 Jan 2019 09:42:17 -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 125621 invoked by uid 48); 22 Jan 2019 09:42:12 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 09:42: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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:
Message-ID: <bug-88952-4-bXNqDYz5pG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg03013.txt.bz2
Content-length: 845

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

--- Comment #7 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to Christopher Leonard from comment #5)
> Is the order at least consistant with x86-32? i.e. if you give a 64-bit
> input operand to inline assembly the order is hi:lo? I'm worried this is a
> bizarre convention imposed on high endian architectures.

On x86, we don't allow register pairs in asm at all. Please see print_reg,
where:

  switch (msize)
    {
    case 16:
    case 12:
    case 8:
      if (GENERAL_REGNO_P (regno) && msize > GET_MODE_SIZE (word_mode))
        warning (0, "unsupported size for integer register");
      /* FALLTHRU */

So, if someone wants to handle DImode on 32bit targets, both registers have to
be passed to assembly explicitly, using "(int) lval" and "(int) (lval >> 32)".
>From gcc-bugs-return-630205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:43:17 2019
Return-Path: <gcc-bugs-return-630205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22065 invoked by alias); 22 Jan 2019 09:43:16 -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 19929 invoked by uid 48); 22 Jan 2019 09:43:12 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 09:43: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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:
Message-ID: <bug-88963-4-lo53BYvGoW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03014.txt.bz2
Content-length: 879

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Devin Hussey from comment #4)
> Strangely, this doesn't seem to affect the ARM or aarch64 backends, although
> I am on a December build (specifically Dec 29). 8.2 is also unaffected.

This is due to those backends support very wide integer modes (OI, etc.).


> aarch64-none-eabi-gcc -O3 -S test.c
> 
> test:
>         ld1     {v16.16b - v19.16b}, [x1]
>         ld1     {v4.16b - v7.16b}, [x2]
>         add     v0.4s, v16.4s, v4.4s
>         add     v1.4s, v17.4s, v5.4s
>         add     v2.4s, v18.4s, v6.4s
>         add     v3.4s, v19.4s, v7.4s
>         st1     {v0.16b - v3.16b}, [x0]
>         ret

This is not really that good code either on most if not all micro-arch of
ARMv8.
Doing, 8 ldr/ld1 and 4 st1 is almost always better.
>From gcc-bugs-return-630206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:44:22 2019
Return-Path: <gcc-bugs-return-630206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26895 invoked by alias); 22 Jan 2019 09:44:22 -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 26795 invoked by uid 48); 22 Jan 2019 09:44:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88422] collect2.exe: fatal error: lto-wrapper returned 1 exit status: file not recognized: file truncated
Date: Tue, 22 Jan 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88422-4-qsmlTn8Prb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88422-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: 2019-01/txt/msg03015.txt.bz2
Content-length: 612

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-22
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Thanks for catching this!  I'll apply the patch.
>From gcc-bugs-return-630207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:49:28 2019
Return-Path: <gcc-bugs-return-630207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43115 invoked by alias); 22 Jan 2019 09:48:52 -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 42818 invoked by uid 55); 22 Jan 2019 09:48:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88422] collect2.exe: fatal error: lto-wrapper returned 1 exit status: file not recognized: file truncated
Date: Tue, 22 Jan 2019 09:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88422-4-EAbSwtBrz4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88422-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: 2019-01/txt/msg03016.txt.bz2
Content-length: 564

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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 22 09:47:52 2019
New Revision: 268141

URL: https://gcc.gnu.org/viewcvs?rev=268141&root=gcc&view=rev
Log:
2019-01-22  Nidal Faour  <nidal.faour@wdc.com>

        PR lto/88422
        * simple-object.c (O_BINARY): Define if not already defined.
        (simple_object_copy_lto_debug_sections): Create file in binary
        mode.

Modified:
    trunk/libiberty/ChangeLog
    trunk/libiberty/simple-object.c
>From gcc-bugs-return-630208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:49:40 2019
Return-Path: <gcc-bugs-return-630208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56911 invoked by alias); 22 Jan 2019 09:49:40 -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 54587 invoked by uid 48); 22 Jan 2019 09:49:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88422] collect2.exe: fatal error: lto-wrapper returned 1 exit status: file not recognized: file truncated
Date: Tue, 22 Jan 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work resolution cf_known_to_fail
Message-ID: <bug-88422-4-lwsuESMPBZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88422-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: 2019-01/txt/msg03017.txt.bz2
Content-length: 544

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
      Known to work|                            |8.2.1, 9.0
         Resolution|---                         |FIXED
      Known to fail|                            |8.2.0

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:50:14 2019
Return-Path: <gcc-bugs-return-630210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58757 invoked by alias); 22 Jan 2019 09:50:13 -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 58366 invoked by uid 48); 22 Jan 2019 09:50:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 09:50: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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:
Message-ID: <bug-88963-4-30gnzYkgA0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03019.txt.bz2
Content-length: 197

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Try using 128 (or 256) and you might see that aarch64 falls down similarly.
>From gcc-bugs-return-630209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:50:09 2019
Return-Path: <gcc-bugs-return-630209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57948 invoked by alias); 22 Jan 2019 09:50:08 -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 57770 invoked by uid 55); 22 Jan 2019 09:50:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88422] collect2.exe: fatal error: lto-wrapper returned 1 exit status: file not recognized: file truncated
Date: Tue, 22 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: lto
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88422-4-uq61VhY6es@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88422-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: 2019-01/txt/msg03018.txt.bz2
Content-length: 597

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

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 22 09:49:27 2019
New Revision: 268142

URL: https://gcc.gnu.org/viewcvs?rev=268142&root=gcc&view=rev
Log:
2019-01-22  Nidal Faour  <nidal.faour@wdc.com>

        PR lto/88422
        * simple-object.c (O_BINARY): Define if not already defined.
        (simple_object_copy_lto_debug_sections): Create file in binary
        mode.

Modified:
    branches/gcc-8-branch/libiberty/ChangeLog
    branches/gcc-8-branch/libiberty/simple-object.c
>From gcc-bugs-return-630211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:57:08 2019
Return-Path: <gcc-bugs-return-630211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74263 invoked by alias); 22 Jan 2019 09:57:07 -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 74221 invoked by uid 48); 22 Jan 2019 09:57:03 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 09:57: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.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:
Message-ID: <bug-88952-4-74n6IHhMaJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg03020.txt.bz2
Content-length: 149

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

--- Comment #8 from Andreas Schwab <schwab@linux-m68k.org> ---
reg:reg+1 maps to lo:hi on x86.
>From gcc-bugs-return-630212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:57:39 2019
Return-Path: <gcc-bugs-return-630212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75177 invoked by alias); 22 Jan 2019 09:57:39 -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 75105 invoked by uid 48); 22 Jan 2019 09:57:34 -0000
From: "christopher.leonard at abaco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 09:57: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christopher.leonard at abaco dot com
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:
Message-ID: <bug-88952-4-mWjtQFGSks@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg03021.txt.bz2
Content-length: 1195

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

--- Comment #9 from Christopher Leonard <christopher.leonard at abaco dot com> ---
(In reply to Andrew Pinski from comment #6)
> Yes the order is always hi:lo (reg:reg+1) on all targets I know of

This is definitely not the natural choice (on any platform: I agree, endianness
is irrelevant here) so I would recommend documenting this as well, and
potentially recommending in the docs to explicitly cast e.g. a parameter for a
function-style macro used as an input operand expression for inline asm, (%L0
is no help when the size is unknown, it seems to select the "next" register
when you give a 32-bit type, which isn't even loaded with a value in the
generated PPC assembly).

This is how the code messed up for me, I wrote a macro function to generate
MTSPR instructions for a given SPR and load value (this is needed since the SPR
number used in MTSPR is immediate, there is not alternative where you can take
the SPR from a register). One of the constants I used in the calculation of an
SPR's load value became a 64-bit type in a later code change, making the input
operand 64-bit instead of 32-bit, breaking my code.
>From gcc-bugs-return-630213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:58:59 2019
Return-Path: <gcc-bugs-return-630213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77282 invoked by alias); 22 Jan 2019 09:58:59 -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 77162 invoked by uid 48); 22 Jan 2019 09:58:55 -0000
From: "christopher.leonard at abaco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 09:58: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christopher.leonard at abaco dot com
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:
Message-ID: <bug-88952-4-3xhFFh2m8m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg03022.txt.bz2
Content-length: 367

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

--- Comment #10 from Christopher Leonard <christopher.leonard at abaco dot com> ---
Getting contradictory statements now:
>reg:reg+1 maps to lo:hi on x86.
>On x86, we don't allow register pairs in asm at all.

Not allowing, or printing a warning, is much better behavior than what I have
been getting on PPC.
>From gcc-bugs-return-630215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:59:47 2019
Return-Path: <gcc-bugs-return-630215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85882 invoked by alias); 22 Jan 2019 09:59:47 -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 85784 invoked by uid 48); 22 Jan 2019 09:59:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Tue, 22 Jan 2019 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to
Message-ID: <bug-88044-4-aS1Rpk8GJv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-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: 2019-01/txt/msg03024.txt.bz2
Content-length: 507

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 09:59:01 2019
Return-Path: <gcc-bugs-return-630214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77481 invoked by alias); 22 Jan 2019 09:59:00 -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 77190 invoked by uid 55); 22 Jan 2019 09:58:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Tue, 22 Jan 2019 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88044-4-TPFU0xcCec@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-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: 2019-01/txt/msg03023.txt.bz2
Content-length: 564

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

--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 09:58:23 2019
New Revision: 268143

URL: https://gcc.gnu.org/viewcvs?rev=268143&root=gcc&view=rev
Log:
        PR tree-optimization/88044
        * tree-ssa-loop-niter.c (number_of_iterations_cond): If condition
        is false in the first iteration, but !every_iteration, return false
        instead of true with niter->niter zero.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/tree-ssa-loop-niter.c
>From gcc-bugs-return-630216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:01:04 2019
Return-Path: <gcc-bugs-return-630216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87985 invoked by alias); 22 Jan 2019 10:01: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 87840 invoked by uid 48); 22 Jan 2019 10:00:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88862] [9 Regression] ICE in extract_affine, at graphite-sese-to-poly.c:313
Date: Tue, 22 Jan 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88862-4-ovdmznOryk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88862-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: 2019-01/txt/msg03025.txt.bz2
Content-length: 262

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Huh.  We get &itarg1 here from originally (integer(kind=4)) &itarg1.  The
stmt we analyze is

  if (_4 != _316)

I have a simple patch.
>From gcc-bugs-return-630217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:01:06 2019
Return-Path: <gcc-bugs-return-630217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88109 invoked by alias); 22 Jan 2019 10:01:05 -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 87899 invoked by uid 48); 22 Jan 2019 10:01:00 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 10:01: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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:
Message-ID: <bug-88963-4-YNjWaNs2ww@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03026.txt.bz2
Content-length: 153

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

--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
See PR 55266 (and several others).
>From gcc-bugs-return-630218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:04:24 2019
Return-Path: <gcc-bugs-return-630218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79818 invoked by alias); 22 Jan 2019 10:04:24 -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 75636 invoked by uid 48); 22 Jan 2019 10:04:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 10:04: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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:
Message-ID: <bug-88963-4-yfjEvdWFDo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03027.txt.bz2
Content-length: 305

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

--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
You can try the attached patch, it "fixes" the issue on the GIMPLE side but
appearantly the BIT_FIELD_REF stores go a weird path during RTL expansion
and so we end up spilling again.
>From gcc-bugs-return-630219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:05:42 2019
Return-Path: <gcc-bugs-return-630219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27235 invoked by alias); 22 Jan 2019 10:05:42 -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 14590 invoked by uid 48); 22 Jan 2019 10:05:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88966] Indirect stringification of "linux" produces "1"
Date: Tue, 22 Jan 2019 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
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: bug_status resolution
Message-ID: <bug-88966-4-ggapD6gDKV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88966-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: 2019-01/txt/msg03028.txt.bz2
Content-length: 610

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is not a bug, "linux" is a predefined macro and the preprocessor is doing
exactly what it's supposed to. See
https://gcc.gnu.org/onlinedocs/cpp/System-specific-Predefined-Macros.html
>From gcc-bugs-return-630220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:14:58 2019
Return-Path: <gcc-bugs-return-630220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22788 invoked by alias); 22 Jan 2019 10:14:57 -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 20254 invoked by uid 48); 22 Jan 2019 10:14:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88897] Bogus maybe-uninitialized warning on class field
Date: Tue, 22 Jan 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88897-4-XjKiD6rce0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88897-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88897-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: 2019-01/txt/msg03029.txt.bz2
Content-length: 1982

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
     Ever confirmed|0                           |1

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
So this boils down to a missed optimization (as many cases do...).  The
uninit warning sees

<bb 2> [local count: 1073741825]:
_3 = bar ();
future_state::future_state (&_local_state);
MEM[(struct  &)&_local_state] ={v} {CLOBBER};
MEM[(struct optional *)&_local_state]._M_engaged = 0;
MEM[(struct optional *)_3]._M_engaged = 0;
_7 = MEM[(struct optional &)&_local_state]._M_engaged;
if (_7 != 0)
  goto <bb 3>; [50.00%]
else
  goto <bb 5>; [50.00%]

<bb 3> [local count: 536870912]:
_6 = MEM[(struct temporary_buffer &)&_local_state]._buffer;
...

and warns about the load _6 = ...

As you can see the condition isn't elided and somehow we didn't manage to CSE
the load of _M_engaged here, possibly due to the appearant aliasing of
the store via _3.  points-to analysis explicitely says it might alias
_local_state because _local_state escapes to future_state::future_state
and PTA is not flow-sensitive:

  <bb 2> [local count: 1073741825]:
  # PT = nonlocal escaped null
  # USE = nonlocal null { D.2493 } (escaped)
  # CLB = nonlocal null { D.2493 } (escaped)
  _3 = bar ();
  # USE = nonlocal null { D.2493 } (escaped)
  # CLB = nonlocal null { D.2493 } (escaped)
  future_state::future_state (&_local_stateD.2493);
  MEM[(struct  &)&_local_stateD.2493] ={v} {CLOBBER};
  MEM[(struct optionalD.2409 *)&_local_stateD.2493]._M_engagedD.2426 = 0;
  MEM[(struct optionalD.2409 *)_3]._M_engagedD.2426 = 0;
>From gcc-bugs-return-630221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:20:00 2019
Return-Path: <gcc-bugs-return-630221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52954 invoked by alias); 22 Jan 2019 10:19:59 -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 52874 invoked by uid 48); 22 Jan 2019 10:19:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88904] [9 Regression] Basic block incorrectly skipped in jump threading.
Date: Tue, 22 Jan 2019 10:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88904-4-5olJAQ1WC4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88904-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: 2019-01/txt/msg03030.txt.bz2
Content-length: 423

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:20:42 2019
Return-Path: <gcc-bugs-return-630222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55951 invoked by alias); 22 Jan 2019 10:20:41 -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 55385 invoked by uid 48); 22 Jan 2019 10:20:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88906] wrong code with -march=k6 -minline-all-stringops -minline-stringops-dynamically -mmemcpy-strategy=libcall:-1:align and vector argument
Date: Tue, 22 Jan 2019 10:20: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: 9.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88906-4-cwbC9raaI3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88906-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: 2019-01/txt/msg03031.txt.bz2
Content-length: 471

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-630223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:22:12 2019
Return-Path: <gcc-bugs-return-630223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107078 invoked by alias); 22 Jan 2019 10:22:11 -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 105319 invoked by uid 48); 22 Jan 2019 10:22:08 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37398] Statement functions mask missing PURE procedures.
Date: Tue, 22 Jan 2019 10:22: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.4.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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:
Message-ID: <bug-37398-4-0lkjoearLn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37398-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: 2019-01/txt/msg03032.txt.bz2
Content-length: 284

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

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> This correctly gives the expected error messages since at least gfortran 5.4.
> Closing as FIXED?

FORALL(i=1:4) a(i) = st3 (i) is still not caught.
>From gcc-bugs-return-630224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:23:05 2019
Return-Path: <gcc-bugs-return-630224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4256 invoked by alias); 22 Jan 2019 10:23:05 -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 1619 invoked by uid 48); 22 Jan 2019 10:23:00 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Tue, 22 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88953-4-oVn3TCo8QY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88953-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: 2019-01/txt/msg03033.txt.bz2
Content-length: 764

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

--- Comment #4 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
Looks like a problem which was fixed with r265158:

    S/390: Fix problem with vec_init expander

    gcc/ChangeLog:

    2018-10-15  Andreas Krebbel  <krebbel@linux.ibm.com>

        * config/s390/s390.c (s390_expand_vec_init): Force vector element
        into reg if it isn't a general operand.

    gcc/testsuite/ChangeLog:

    2018-10-15  Andreas Krebbel  <krebbel@linux.ibm.com>

        * g++.dg/vec-init-1.C: New test.



I've backported the patch to GCC 7 and 8 branch on 2018-10-19. Canonical is
aware of the problem and will pick the patch up for their next GCC updates.

Could you please check whether this fixes your problem?
>From gcc-bugs-return-630226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:38:27 2019
Return-Path: <gcc-bugs-return-630226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98948 invoked by alias); 22 Jan 2019 10:38:27 -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 98890 invoked by uid 48); 22 Jan 2019 10:38:23 -0000
From: "maratrus at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88971] New: Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: maratrus at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88971-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: 2019-01/txt/msg03035.txt.bz2
Content-length: 1292

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

            Bug ID: 88971
           Summary: Branch optimization inconsistency (missed
                    optimization)
           Product: gcc
           Version: 8.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: maratrus at mail dot ru
  Target Milestone: ---

Created attachment 45490
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45490&action=edit
A code that demonstrates different patterns in optimization technique

In the code attached I expect the compiler not to generate any code between two
`mfence` instructions in the method `CheckAndPrint()`.

Indeed, it does the good job if I call `PrintGood<false>()` method and no code
is generated. But if I out-comment `PrintBad<false>()` or even simple return
the compiler generates a code for the if-expression `if (t.j > 0)`.

In all three cases there seems to be no reason to generate any code.

The code attached is compiled as:

`g++ -std=c++11 -Ofast opt_template.cc -o opt_template`

I must be missing something but is there a good reason why the compiler managed
to optimize the code in one case but non in the other two?
>From gcc-bugs-return-630225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:38:16 2019
Return-Path: <gcc-bugs-return-630225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98210 invoked by alias); 22 Jan 2019 10:38:15 -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 98033 invoked by uid 48); 22 Jan 2019 10:38:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88964-4-n8jSgQMREk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03034.txt.bz2
Content-length: 1172

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |jakub at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
--- gcc/gimple-loop-interchange.cc.jj   2019-01-01 12:37:17.416970701 +0100
+++ gcc/gimple-loop-interchange.cc      2019-01-22 11:34:42.303796570 +0100
@@ -692,7 +692,7 @@ loop_cand::analyze_induction_var (tree v
       iv->var = var;
       iv->init_val = init;
       iv->init_expr = chrec;
-      iv->step = build_int_cst (TREE_TYPE (chrec), 0);
+      iv->step = build_zero_cst (TREE_TYPE (chrec));
       m_inductions.safe_push (iv);
       return true;
     }

fixes this.  SCEV is able to deal with non-integral/pointer IVs like
SCALAR_FLOAT_TYPE_P in this case and create_iv as well, just build_int_cst must
not be used in that case.
>From gcc-bugs-return-630227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:39:36 2019
Return-Path: <gcc-bugs-return-630227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101904 invoked by alias); 22 Jan 2019 10:39:36 -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 101452 invoked by uid 48); 22 Jan 2019 10:39:32 -0000
From: "Jan.Kossmann at hpi dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Tue, 22 Jan 2019 10:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Jan.Kossmann at hpi dot de
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88953-4-jcGjLBTqnB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88953-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: 2019-01/txt/msg03036.txt.bz2
Content-length: 643

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

--- Comment #5 from Jan Kossmann <Jan.Kossmann at hpi dot de> ---
You are right, I verified with:

gcc version 9.0.0 20190122 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O3'  '-o' 'test.cpp.o'
'-shared-libgcc' '-march=z13' '-mno-htm' '-mzarch' '-m64'
 gcc/bin/../libexec/gcc/s390x-ibm-linux-gnu/9.0.0/cc1plus -E -quiet -v
-imultiarch s390x-linux-gnu -iprefix
gcc/bin/../lib/gcc/s390x-ibm-linux-gnu/9.0.0/ -D_GNU_SOURCE test.cpp -march=z13
-mno-htm -mzarch -m64 -O3 -fpch-preprocess -o test.ii

and it worked out fine. Sorry for the trouble, thanks for your help!
>From gcc-bugs-return-630229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:46:53 2019
Return-Path: <gcc-bugs-return-630229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5369 invoked by alias); 22 Jan 2019 10:46:53 -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 5257 invoked by uid 48); 22 Jan 2019 10:46:49 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-yAO89n4lfM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03038.txt.bz2
Content-length: 1345

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

--- Comment #24 from Chris Elrod <elrodc at gmail dot com> ---
The dump looks like this:

  vect__67.78_217 = SQRT (vect__213.77_225);
  vect_ui33_68.79_248 = { 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0,
1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0
} / vect__67.78_217;
  vect__71.80_249 = vect__246.59_65 * vect_ui33_68.79_248;
  vect_u13_73.81_250 = vect__187.71_14 * vect_ui33_68.79_248;
  vect_u23_75.82_251 = vect__200.74_5 * vect_ui33_68.79_248;

so the vrsqrt optimization happens later. g++ shows the same problems with
weird code generation. However this:

 /* sqrt(a)  = -0.5 * a * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0)
    rsqrt(a) = -0.5     * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0) */

does not match this:

        vrsqrt14ps      %zmm1, %zmm2 # comparison and mask removed
        vmulps  %zmm1, %zmm2, %zmm0
        vmulps  %zmm2, %zmm0, %zmm1
        vmulps  %zmm6, %zmm0, %zmm0
        vaddps  %zmm7, %zmm1, %zmm1
        vmulps  %zmm0, %zmm1, %zmm1
        vrcp14ps        %zmm1, %zmm0
        vmulps  %zmm1, %zmm0, %zmm1
        vmulps  %zmm1, %zmm0, %zmm1
        vaddps  %zmm0, %zmm0, %zmm0
        vsubps  %zmm1, %zmm0, %zmm0

Recommendations on the next place to look for what's going on?
>From gcc-bugs-return-630228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:46:12 2019
Return-Path: <gcc-bugs-return-630228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123270 invoked by alias); 22 Jan 2019 10:46:11 -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 122797 invoked by uid 48); 22 Jan 2019 10:45:50 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88948] [9 Regression] ICE in elimination_costs_in_insn, at reload1.c:3640 since r264148
Date: Tue, 22 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88948-4-A8PeBsgGla@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88948-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: 2019-01/txt/msg03037.txt.bz2
Content-length: 1173

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

--- Comment #2 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
The problem is with can_assign_to_reg_without_clobbers_p in gcse.c, where we
have:

  /* If the test insn is valid and doesn't need clobbers, and the target also
     has no objections, we're good.  */
  if (icode >= 0
      && (num_clobbers == 0 || !added_clobbers_hard_reg_p (icode))
      && ! (targetm.cannot_copy_insn_p
            && targetm.cannot_copy_insn_p (test_insn)))
    can_assign = true;

The test instruction is created as:

(insn 26 0 0 (set (reg:SI 152)
        (fix:SI (reg:DF 89))) -1
     (nil))

which is (correctly) recognized as

(define_insn "fix_trunc<mode>_i387_fisttp"
  [(set (match_operand:SWI248x 0 "nonimmediate_operand" "=m")
        (fix:SWI248x (match_operand 1 "register_operand" "f")))
   (clobber (match_scratch:XF 2 "=&f"))]

However, recog also reports that 1 clobber needs to be added. The instruction
is recognized nevertheless due to "|| !added_clobbers_hard_reg_p (icode)"
bypass. The recognized insn doesn't clobber hard reg, but it also needs a
clobber of a scratch reg to be recognized.
>From gcc-bugs-return-630230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:47:06 2019
Return-Path: <gcc-bugs-return-630230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10266 invoked by alias); 22 Jan 2019 10:47:05 -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 8094 invoked by uid 48); 22 Jan 2019 10:47:02 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Tue, 22 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88950-4-yhE8T8sWw0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88950-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: 2019-01/txt/msg03039.txt.bz2
Content-length: 545

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

ktkachov at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|2019-01-21 00:00:00         |2019-01-22
                 CC|                            |ktkachov at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #4 from ktkachov at gcc dot gnu.org ---
Confirmed on aarch64 then.
>From gcc-bugs-return-630231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:49:29 2019
Return-Path: <gcc-bugs-return-630231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20180 invoked by alias); 22 Jan 2019 10:49:28 -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 20116 invoked by uid 48); 22 Jan 2019 10:49:25 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88972] New: popcnt of limited 128-bit number with unnecessary zeroing
Date: Tue, 22 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88972-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: 2019-01/txt/msg03040.txt.bz2
Content-length: 1475

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

            Bug ID: 88972
           Summary: popcnt of limited 128-bit number with unnecessary
                    zeroing
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: drepper.fsp+rhbz at gmail dot com
  Target Milestone: ---

Compile the following code on x86-64 with -Ofast -march=haswell:

int f(__uint128_t m)
{
  if (m < 64000)
    return __builtin_popcount(m);
  return -1;
}


The generated code with the trunk gcc looks like this:

   0:   b8 ff f9 00 00          mov    $0xf9ff,%eax
   5:   48 39 f8                cmp    %rdi,%rax
   8:   b8 00 00 00 00          mov    $0x0,%eax
   d:   48 19 f0                sbb    %rsi,%rax
  10:   72 0e                   jb     20 <f+0x20>
  12:   31 c0                   xor    %eax,%eax
  14:   f3 0f b8 c7             popcnt %edi,%eax
  18:   c3                      retq   
  19:   0f 1f 80 00 00 00 00    nopl   0x0(%rax)
  20:   b8 ff ff ff ff          mov    $0xffffffff,%eax
  25:   c3                      retq   


The instruction at offset 12 is unnecessary.  I guess this is a left-over from
the popcnt of the upper half which is recognized to be unnecessary and left
out.  There is no addition anymore but somehow the register clearing survived.
>From gcc-bugs-return-630232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:56:45 2019
Return-Path: <gcc-bugs-return-630232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28536 invoked by alias); 22 Jan 2019 10:56:44 -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 28433 invoked by uid 55); 22 Jan 2019 10:56:39 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 10:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-JqWfImHPsc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03041.txt.bz2
Content-length: 1724

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

--- Comment #25 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, elrodc at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #24 from Chris Elrod <elrodc at gmail dot com> ---
> The dump looks like this:
> 
>   vect__67.78_217 = SQRT (vect__213.77_225);
>   vect_ui33_68.79_248 = { 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0,
> 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0
> } / vect__67.78_217;
>   vect__71.80_249 = vect__246.59_65 * vect_ui33_68.79_248;
>   vect_u13_73.81_250 = vect__187.71_14 * vect_ui33_68.79_248;
>   vect_u23_75.82_251 = vect__200.74_5 * vect_ui33_68.79_248;
> 
> so the vrsqrt optimization happens later. g++ shows the same problems with
> weird code generation. However this:
> 
>  /* sqrt(a)  = -0.5 * a * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0)
>     rsqrt(a) = -0.5     * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0) */
> 
> does not match this:
> 
>         vrsqrt14ps      %zmm1, %zmm2 # comparison and mask removed
>         vmulps  %zmm1, %zmm2, %zmm0
>         vmulps  %zmm2, %zmm0, %zmm1
>         vmulps  %zmm6, %zmm0, %zmm0
>         vaddps  %zmm7, %zmm1, %zmm1
>         vmulps  %zmm0, %zmm1, %zmm1
>         vrcp14ps        %zmm1, %zmm0
>         vmulps  %zmm1, %zmm0, %zmm1
>         vmulps  %zmm1, %zmm0, %zmm1
>         vaddps  %zmm0, %zmm0, %zmm0
>         vsubps  %zmm1, %zmm0, %zmm0
> 
> Recommendations on the next place to look for what's going on?

You can try enabling -mrecip to see RSQRT in .optimized - there's
probably late 1/sqrt optimization on RTL.
>From gcc-bugs-return-630233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:57:07 2019
Return-Path: <gcc-bugs-return-630233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32789 invoked by alias); 22 Jan 2019 10:57:07 -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 30011 invoked by uid 48); 22 Jan 2019 10:57:03 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 10:57: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
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:
Message-ID: <bug-88963-4-gWo1QKCmFR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03042.txt.bz2
Content-length: 1914

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

--- Comment #9 from Devin Hussey <husseydevin at gmail dot com> ---
(In reply to Andrew Pinski from comment #6)
> Try using 128 (or 256) and you might see that aarch64 falls down similarly.

yup. Oof.

test:
        sub     sp, sp, #560
        stp     x29, x30, [sp]
        mov     x29, sp
        stp     x19, x20, [sp, 16]
        mov     x19, 128
        mov     x20, x0
        add     x0, sp, 176
        str     x21, [sp, 32]
        mov     x21, x2
        mov     x2, x19
        bl      memcpy
        mov     x2, x19
        mov     x1, x21
        add     x0, sp, 304
        bl      memcpy
        ldr     q7, [sp, 176]
        mov     x2, x19
        ldr     q6, [sp, 192]
        add     x1, sp, 48
        ldr     q5, [sp, 208]
        mov     x0, x20
        ldr     q4, [sp, 224]
        ldr     q3, [sp, 240]
        ldr     q2, [sp, 256]
        ldr     q1, [sp, 272]
        ldr     q0, [sp, 288]
        ldr     q23, [sp, 304]
        ldr     q22, [sp, 320]
        ldr     q21, [sp, 336]
        ldr     q20, [sp, 352]
        ldr     q19, [sp, 368]
        ldr     q18, [sp, 384]
        ldr     q17, [sp, 400]
        ldr     q16, [sp, 416]
        add     v7.4s, v7.4s, v23.4s
        add     v6.4s, v6.4s, v22.4s
        add     v5.4s, v5.4s, v21.4s
        add     v4.4s, v4.4s, v20.4s
        add     v3.4s, v3.4s, v19.4s
        str     q7, [sp, 48]
        add     v2.4s, v2.4s, v18.4s
        str     q6, [sp, 64]
        add     v1.4s, v1.4s, v17.4s
        str     q5, [sp, 80]
        add     v0.4s, v0.4s, v16.4s
        str     q4, [sp, 96]
        str     q3, [sp, 112]
        str     q2, [sp, 128]
        str     q1, [sp, 144]
        str     q0, [sp, 160]
        bl      memcpy
        ldp     x29, x30, [sp]
        ldp     x19, x20, [sp, 16]
        ldr     x21, [sp, 32]
        add     sp, sp, 560
        ret
>From gcc-bugs-return-630234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:58:08 2019
Return-Path: <gcc-bugs-return-630234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75526 invoked by alias); 22 Jan 2019 10:58:08 -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 66608 invoked by uid 48); 22 Jan 2019 10:58:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88953] Unrecognizable insn on architecture zEC12 with boost::bimap
Date: Tue, 22 Jan 2019 10:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-88953-4-NrDzuDAA35@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88953-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: 2019-01/txt/msg03043.txt.bz2
Content-length: 451

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed then on all active branches.
>From gcc-bugs-return-630235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 10:58:53 2019
Return-Path: <gcc-bugs-return-630235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115263 invoked by alias); 22 Jan 2019 10:58:52 -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 115160 invoked by uid 48); 22 Jan 2019 10:58:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 10:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88964-4-mhSq6kOJW8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03044.txt.bz2
Content-length: 253

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45491
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45491&action=edit
gcc9-pr88964.patch

Untested fix.
>From gcc-bugs-return-630236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:02:01 2019
Return-Path: <gcc-bugs-return-630236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121334 invoked by alias); 22 Jan 2019 11:01:59 -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 120725 invoked by uid 48); 22 Jan 2019 11:01:49 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-dmdPRsoFyN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03045.txt.bz2
Content-length: 1542

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

--- Comment #26 from Chris Elrod <elrodc at gmail dot com> ---
> You can try enabling -mrecip to see RSQRT in .optimized - there's
> probably late 1/sqrt optimization on RTL.

No luck. The full commands I used:

gfortran -Ofast -mrecip -S -fdump-tree-optimized -march=native -shared -fPIC
-mprefer-vector-width=512 -fno-semantic-interposition -o
gfortvectorizationdump.s  vectorization_test.f90

g++ -mrecip -Ofast -fdump-tree-optimized -S -march=native -shared -fPIC
-mprefer-vector-width=512 -fno-semantic-interposition -o
gppvectorization_test.s  vectorization_test.cpp

g++'s output was similar:

  vect_U33_60.31_372 = SQRT (vect_S33_59.30_371);
  vect_Ui33_61.32_374 = { 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0,
1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0, 1.0e+0
} / vect_U33_60.31_372;
  vect_U13_62.33_375 = vect_S13_47.24_359 * vect_Ui33_61.32_374;
  vect_U23_63.34_376 = vect_S23_53.27_365 * vect_Ui33_61.32_374;

and it has the same assembly as gfortran for the rsqrt:

        vcmpps  $4, %zmm0, %zmm5, %k1
        vrsqrt14ps      %zmm0, %zmm1{%k1}{z}
        vmulps  %zmm0, %zmm1, %zmm2
        vmulps  %zmm1, %zmm2, %zmm0
        vmulps  %zmm6, %zmm2, %zmm2
        vaddps  %zmm7, %zmm0, %zmm0
        vmulps  %zmm2, %zmm0, %zmm0
        vrcp14ps        %zmm0, %zmm10
        vmulps  %zmm0, %zmm10, %zmm0
        vmulps  %zmm0, %zmm10, %zmm0
        vaddps  %zmm10, %zmm10, %zmm10
        vsubps  %zmm0, %zmm10, %zmm10
>From gcc-bugs-return-630237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:04:19 2019
Return-Path: <gcc-bugs-return-630237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21347 invoked by alias); 22 Jan 2019 11:04:19 -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 21012 invoked by uid 48); 22 Jan 2019 11:04:09 -0000
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88950] stack_protect_prologue can be reordered by sched1 around memory accesses
Date: Tue, 22 Jan 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matmal01 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: cf_known_to_fail
Message-ID: <bug-88950-4-KAcOPtYkJw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88950-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: 2019-01/txt/msg03046.txt.bz2
Content-length: 2444

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

Matthew Malcomson <matmal01 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |5.4.0

--- Comment #5 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
This problem has been around for a long time -- I have seen the same
fundamental problem on gcc 5.4 (when looking for a version to put in the "known
to work" field).

With   "gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609" on the same
testcase, the stack_protect_test pattern gets reordered to before the second
memory access (the "buf[b] = c" line), and again the stack protection does not
guard this memory access.


(insn:TI 8 126 16 (parallel [
            (set (mem/v/f/c:DI (plus:DI (reg/f:DI 29 x29)
                        (const_int 88 [0x58])) [1 D.2834+0 S8 A64])
                (unspec:DI [
                        (mem/v/f/c:DI (reg/f:DI 3 x3 [100]) [1
__stack_chk_guard+0 S8 A64])
                    ] UNSPEC_SP_SET))
            (set (reg:DI 5 x5 [126])
                (const_int 0 [0]))
        ]) stack-reorder.c:1 864 {stack_protect_set_di}
     (expr_list:REG_UNUSED (reg:DI 5 x5 [126])
        (nil)))
(insn:TI 16 8 71 (set (mem/j:QI (plus:DI (reg:DI 0 x0 [105])
                (const_int 4016 [0xfb0])) [0 buf S1 A8])
        (reg:QI 4 x4 [106])) stack-reorder.c:3 45 {*movqi_aarch64}
     (expr_list:REG_DEAD (reg:QI 4 x4 [106])
        (expr_list:REG_DEAD (reg:DI 0 x0 [105])
            (nil))))
(insn 71 16 22 (parallel [
            (set (reg:DI 3 x3 [125])
                (unspec:DI [
                        (mem/v/f/c:DI (plus:DI (reg/f:DI 29 x29)
                                (const_int 88 [0x58])) [1 D.2834+0 S8 A64])
                        (mem/v/f/c:DI (reg/f:DI 3 x3 [100]) [1
__stack_chk_guard+0 S8 A64])
                    ] UNSPEC_SP_TEST))
            (clobber (reg:DI 0 x0 [127]))
        ]) stack-reorder.c:14 866 {stack_protect_test_di}
     (expr_list:REG_UNUSED (reg:DI 0 x0 [127])
        (nil)))
(insn:TI 22 71 140 (set (mem/j:QI (plus:DI (reg:DI 1 x1 [110])
                (const_int 4016 [0xfb0])) [0 buf S1 A8])
        (reg:QI 2 x2 [ c ])) stack-reorder.c:4 45 {*movqi_aarch64}
     (expr_list:REG_DEAD (reg:QI 2 x2 [ c ])
        (expr_list:REG_DEAD (reg:DI 1 x1 [110])
            (nil))))
>From gcc-bugs-return-630238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:13:47 2019
Return-Path: <gcc-bugs-return-630238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80212 invoked by alias); 22 Jan 2019 11:13:47 -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 80163 invoked by uid 48); 22 Jan 2019 11:13:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Tue, 22 Jan 2019 11:13: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88954-4-dlAd31c5Nk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg03047.txt.bz2
Content-length: 351

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
For indirect calls the attributes on the function type pointed to a relevant. 
Unioning attributes from the actually called function (if the compiler can
figure that out) can be appropriate depending on the actual attribute.
>From gcc-bugs-return-630239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:17:18 2019
Return-Path: <gcc-bugs-return-630239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96416 invoked by alias); 22 Jan 2019 11:17:17 -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 95278 invoked by uid 48); 22 Jan 2019 11:17:07 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-yo4Bq7aVER@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03048.txt.bz2
Content-length: 524

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

--- Comment #27 from Chris Elrod <elrodc at gmail dot com> ---
g++ -mrecip=all -O3  -fno-signed-zeros -fassociative-math -freciprocal-math
-fno-math-errno -ffinite-math-only -fno-trapping-math -fdump-tree-optimized -S
-march=native -shared -fPIC -mprefer-vector-width=512
-fno-semantic-interposition -o gppvectorization_test.s  vectorization_test.cpp

is not enough to get vrsqrt. I need -funsafe-math-optimizations for the
instruction to appear in the asm.
>From gcc-bugs-return-630240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:19:21 2019
Return-Path: <gcc-bugs-return-630240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102461 invoked by alias); 22 Jan 2019 11:19: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 102409 invoked by uid 48); 22 Jan 2019 11:19:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88973] New: New -Wrestrict warning since r268048
Date: Tue, 22 Jan 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-88973-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: 2019-01/txt/msg03049.txt.bz2
Content-length: 1388

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

            Bug ID: 88973
           Summary: New -Wrestrict warning since r268048
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: msebor at gcc dot gnu.org
  Target Milestone: ---

Created attachment 45492
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45492&action=edit
test-case

The test-case comes from autogen package:

$ gcc autogen.i -c -O2 -Werror=restrict
In function â€˜strcpyâ€™,
    inlined from â€˜canonicalize_pathnameâ€™ at autogen.i:10536:17,
    inlined from â€˜option_pathfind.constpropâ€™ at autogen.i:10420:32:
autogen.i:4050:10: error: â€˜__builtin_strcpyâ€™ accessing 1 byte at offsets [0,
9223372036854775807] and [0, 9223372036854775807] may overlap 1 byte at offset
0 [-Werror=restrict]
 4050 |   return __builtin___strcpy_chk (__dest, __src, __builtin_object_size
(__dest, 2 > 1));
      |         
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors

Martin can you please verify that the warning is correct?
>From gcc-bugs-return-630241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:23:53 2019
Return-Path: <gcc-bugs-return-630241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128876 invoked by alias); 22 Jan 2019 11:23:53 -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 128823 invoked by uid 48); 22 Jan 2019 11:23:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88955] transparent_union for vector types not accepted
Date: Tue, 22 Jan 2019 11:23: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88955-4-SPLVaK1h3G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88955-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: 2019-01/txt/msg03050.txt.bz2
Content-length: 2381

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |rejects-valid
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
                 CC|                            |hjl.tools at gmail dot com,
                   |                            |jsm28 at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm.  I guess the "issue" is that the union has TImode rather than V2DImode.
stor-layout doesn't look at TYPE_TRANSPARENT_AGGR at all though.  Relevant
is

  /* If we only have one real field; use its mode if that mode's size
     matches the type's size.  This generally only applies to RECORD_TYPE.
     For UNION_TYPE, if the widest field is MODE_INT then use that mode.
     If the widest field is MODE_PARTIAL_INT, and the union will be passed
     by reference, then use that mode.  */
  poly_uint64 type_size;
  if ((TREE_CODE (type) == RECORD_TYPE
       || (TREE_CODE (type) == UNION_TYPE
           && (GET_MODE_CLASS (mode) == MODE_INT
               || (GET_MODE_CLASS (mode) == MODE_PARTIAL_INT
                   && targetm.calls.pass_by_reference (pack_cumulative_args
(0),
                                                       mode, type, 0)))))
      && mode != VOIDmode
      && poly_int_tree_p (TYPE_SIZE (type), &type_size)
      && known_eq (GET_MODE_BITSIZE (mode), type_size))
    ;
  else
    mode = mode_for_size_tree (TYPE_SIZE (type), MODE_INT, 1).else_blk ();

where we reject vector modes.  The C++ diagnostic is a bit more clear:

> g++ t.c -S
t.c:5:1: error: type transparent â€˜union<anonymous>â€™ cannot be made transparent
because the type of the first field has a different ABI from the class overall
 {
 ^

which hints at the implementation of the argument passing being the culprit
for the restriction (not sure why the ABI of the class overall should matter
given the docs of transparent_union say the ABI is specified by the first
field...)
>From gcc-bugs-return-630243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:29:33 2019
Return-Path: <gcc-bugs-return-630243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9406 invoked by alias); 22 Jan 2019 11:29:32 -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 9339 invoked by uid 55); 22 Jan 2019 11:29:28 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88862] [9 Regression] ICE in extract_affine, at graphite-sese-to-poly.c:313
Date: Tue, 22 Jan 2019 11:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88862-4-lmHC9hJFqD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88862-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: 2019-01/txt/msg03052.txt.bz2
Content-length: 532

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 22 11:28:56 2019
New Revision: 268147

URL: https://gcc.gnu.org/viewcvs?rev=268147&root=gcc&view=rev
Log:
2019-01-22  Richard Biener  <rguenther@suse.de>

        PR tree-optimization/88862
        * graphite-scop-detection.c
        (scop_detection::graphite_can_represent_scev): Reject ADDR_EXPR.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/graphite-scop-detection.c
>From gcc-bugs-return-630242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:29:09 2019
Return-Path: <gcc-bugs-return-630242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8336 invoked by alias); 22 Jan 2019 11:29:08 -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 8253 invoked by uid 48); 22 Jan 2019 11:29:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88862] [9 Regression] ICE in extract_affine, at graphite-sese-to-poly.c:313
Date: Tue, 22 Jan 2019 11:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88862-4-qhPMw43pgm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88862-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: 2019-01/txt/msg03051.txt.bz2
Content-length: 429

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:32:10 2019
Return-Path: <gcc-bugs-return-630244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14058 invoked by alias); 22 Jan 2019 11:32:09 -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 13457 invoked by uid 48); 22 Jan 2019 11:32:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 11:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88964-4-M5LzK1q14E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03053.txt.bz2
Content-length: 274

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, I wonder if handling FP inductions during interchange causes correctness
issues as well (FP rounding, etc.).  Otherwise the patch looks obvious.
>From gcc-bugs-return-630245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:33:22 2019
Return-Path: <gcc-bugs-return-630245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20445 invoked by alias); 22 Jan 2019 11:33: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 20388 invoked by uid 48); 22 Jan 2019 11:33:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 11:33: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88965-4-m87fRHQhlV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg03054.txt.bz2
Content-length: 127

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
LGTM
>From gcc-bugs-return-630246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:33:53 2019
Return-Path: <gcc-bugs-return-630246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21347 invoked by alias); 22 Jan 2019 11:33:52 -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 21272 invoked by uid 48); 22 Jan 2019 11:33:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88968] [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 11:33: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: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88968-4-dU78kGuaye@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg03055.txt.bz2
Content-length: 292

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
>From gcc-bugs-return-630247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:34:51 2019
Return-Path: <gcc-bugs-return-630247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22634 invoked by alias); 22 Jan 2019 11:34: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 22569 invoked by uid 48); 22 Jan 2019 11:34:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88969] [9 Regression] ICE in build_op_delete_call, at cp/call.c:6509
Date: Tue, 22 Jan 2019 11:34: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone short_desc
Message-ID: <bug-88969-4-0Hm5AksNZK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88969-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: 2019-01/txt/msg03056.txt.bz2
Content-length: 554

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
   Target Milestone|---                         |9.0
            Summary|ICE in                      |[9 Regression] ICE in
                   |build_op_delete_call, at    |build_op_delete_call, at
                   |cp/call.c:6509              |cp/call.c:6509
>From gcc-bugs-return-630248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:35:16 2019
Return-Path: <gcc-bugs-return-630248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24909 invoked by alias); 22 Jan 2019 11:35:16 -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 24665 invoked by uid 48); 22 Jan 2019 11:35:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88964-4-Kv2qPUmmbP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03057.txt.bz2
Content-length: 383

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In the spot which I'm changing IMHO shouldn't, that + 0.0 really should be
folded (and if not, we should tweak create_iv not to do any addition if
real_zerop).  Though of course for other floating point IVs where the step is
non-zero it could make a difference.
>From gcc-bugs-return-630249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:38:34 2019
Return-Path: <gcc-bugs-return-630249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29481 invoked by alias); 22 Jan 2019 11:38:34 -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 29379 invoked by uid 48); 22 Jan 2019 11:38:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88970] ICE: verify_ssa failed (error: definition in block 2 follows the use)
Date: Tue, 22 Jan 2019 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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 version
Message-ID: <bug-88970-4-2MmioqVuU7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88970-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88970-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: 2019-01/txt/msg03058.txt.bz2
Content-length: 1067

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org
            Version|unknown                     |9.0

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Looks like a missing/incomplete DECL_EXPR.

;; Function void d() (null)
;; enabled by -tree-original


{
  typedef int e[0:(sizetype) SAVE_EXPR <D.2306>];
^^^ shouldn't this have (ssizetype) b<int> (1) + -1)?

  int f[0:(sizetype) SAVE_EXPR <D.2306>];
  int c;
  typedef struct __lambda0 __lambda0;

    ssizetype D.2306;
  <<cleanup_point <<< Unknown tree: expr_stmt
  (void) (D.2306 = (ssizetype) b<int> (1) + -1) >>>>>;
  <<cleanup_point   int f[0:(sizetype) SAVE_EXPR <D.2306>];>>;
    int c;
  <<cleanup_point <<< Unknown tree: expr_stmt
  d()::<lambda()>::operator() (&TARGET_EXPR <D.2340, {.__c=(int &) &c}>) >>>>>;
}
>From gcc-bugs-return-630250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:48:59 2019
Return-Path: <gcc-bugs-return-630250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88036 invoked by alias); 22 Jan 2019 11:48:58 -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 87943 invoked by uid 48); 22 Jan 2019 11:48:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 11:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords cc component
Message-ID: <bug-88971-4-bRWIvNZg7F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03059.txt.bz2
Content-length: 2250

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
                 CC|                            |rguenth at gcc dot gnu.org
          Component|c++                         |libstdc++

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
This is because it still needs to generate the std::string objects at the
caller
site (outside of the if (print)).  This involves quite some code to get
rid of, and even at -O3 we do not inline basic_string::basic_string it seems
(ISTR that is out-of-line in the library):

  __asm__ __volatile__("mfence" :  :  : "memory");
  _6 = MEM[(const int *)&data + 4B];
  if (_6 > 0)
    goto <bb 3>; [41.48%]
  else
    goto <bb 11>; [58.52%]

  <bb 3> [local count: 445388109]:
  std::basic_string<char>::basic_string (&D.39204, "<", &D.39205);
  _7 = MEM[(char * *)&D.39204];
  _8 = _7 + 18446744073709551592;
  if (_8 != &_S_empty_rep_storage)
    goto <bb 5>; [10.00%]
  else
    goto <bb 4>; [90.00%]

  <bb 4> [local count: 434030711]:
  goto <bb 10>; [100.00%]

  <bb 5> [local count: 44538811]:
  if (__gthrw___pthread_key_create != 0B)
    goto <bb 6>; [53.47%]
  else
    goto <bb 7>; [46.53%]

  <bb 6> [local count: 23814902]:
  _9 = &MEM[(struct _Rep *)_7 + -24B].D.23940._M_refcount;
  _10 = __atomic_fetch_add_4 (_9, 4294967295, 4);
  _11 = (int) _10;
  goto <bb 8>; [100.00%]

  <bb 7> [local count: 20723909]:
  __result_12 = MEM[(_Atomic_word *)_7 + -8B];
  _13 = __result_12 + -1;
  MEM[(_Atomic_word *)_7 + -8B] = _13;

  <bb 8> [local count: 44538811]:
  # _14 = PHI <_11(6), __result_12(7)>
  if (_14 <= 0)
    goto <bb 9>; [25.50%]
  else
    goto <bb 4>; [74.50%]

  <bb 9> [local count: 11357397]:
  std::basic_string<char>::_Rep::_M_destroy (_8, &D.39206);

  <bb 10> [local count: 445388108]:
  D.39206 ={v} {CLOBBER};
  D.39204 ={v} {CLOBBER};
  D.39205 ={v} {CLOBBER};

  <bb 11> [local count: 1073741825]:
  __asm__ __volatile__("mfence" :  :  : "memory");
  data ={v} {CLOBBER};
>From gcc-bugs-return-630252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:54:30 2019
Return-Path: <gcc-bugs-return-630252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121365 invoked by alias); 22 Jan 2019 11:54:29 -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 121264 invoked by uid 48); 22 Jan 2019 11:54:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88964-4-dEfANaFCMF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03061.txt.bz2
Content-length: 354

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Actually no, with HONOR_SIGNED_ZEROS it shouldn't be optimized out.
So, if we don't have other way how to make distinction between a normal chrec
with step +0.0 and loop invariant var, we should punt at least for
HONOR_SIGNED_ZEROS.
>From gcc-bugs-return-630251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:54:18 2019
Return-Path: <gcc-bugs-return-630251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120548 invoked by alias); 22 Jan 2019 11:54:17 -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 120507 invoked by uid 48); 22 Jan 2019 11:54:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88972] popcnt of limited 128-bit number with unnecessary zeroing
Date: Tue, 22 Jan 2019 11:54: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: keywords cf_gcctarget bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-88972-4-rBw3X8hv8O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88972-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88972-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: 2019-01/txt/msg03060.txt.bz2
Content-length: 990

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Target|                            |x86_64-*-*, i?86-*-*
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
          Component|tree-optimization           |target
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Err, __builtin_popcount has an integer argument so you call popcount on
(int)m.  The reason must be different.

(insn 17 16 26 4 (parallel [
            (set (reg:SI 88 [ <retval> ])
                (popcount:SI (subreg:SI (reg/v:TI 89 [ m ]) 0)))
            (clobber (reg:CC 17 flags))
        ]) "t.c":4 -1
     (nil))
>From gcc-bugs-return-630253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 11:57:54 2019
Return-Path: <gcc-bugs-return-630253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81607 invoked by alias); 22 Jan 2019 11:57:53 -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 77504 invoked by uid 48); 22 Jan 2019 11:57:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88973] [8/9 Regression] New -Wrestrict warning since r268048
Date: Tue, 22 Jan 2019 11:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-88973-4-BFGM8AOoN2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88973-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: 2019-01/txt/msg03062.txt.bz2
Content-length: 830

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
           Priority|P3                          |P2
      Known to work|                            |8.2.0
   Target Milestone|---                         |8.3
            Summary|New -Wrestrict warning      |[8/9 Regression] New
                   |since r268048               |-Wrestrict warning since
                   |                            |r268048
      Known to fail|                            |8.2.1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I believe the change was backported as well.
>From gcc-bugs-return-630254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:00:01 2019
Return-Path: <gcc-bugs-return-630254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25500 invoked by alias); 22 Jan 2019 12:00:01 -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 25407 invoked by uid 48); 22 Jan 2019 11:59:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Tue, 22 Jan 2019 12:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-88964-4-Ppucp1y3LZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03063.txt.bz2
Content-length: 539

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45491|0                           |1
        is obsolete|                            |

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45493
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45493&action=edit
gcc9-pr88964.patch

Updated patch.
>From gcc-bugs-return-630255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:08:52 2019
Return-Path: <gcc-bugs-return-630255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81718 invoked by alias); 22 Jan 2019 12:08:52 -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 79151 invoked by uid 48); 22 Jan 2019 12:08:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 12:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88971-4-VkcQrboJSm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03064.txt.bz2
Content-length: 522

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> rid of, and even at -O3 we do not inline basic_string::basic_string it seems
> (ISTR that is out-of-line in the library):

There's an explicit instantiation in the library, but the definition is inline
in the headers. If the compiler wanted to inline it, all the code is visible
and nothing forces it to use the explicit instantiation in the library.
>From gcc-bugs-return-630256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:10:34 2019
Return-Path: <gcc-bugs-return-630256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11957 invoked by alias); 22 Jan 2019 12:10:33 -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 7796 invoked by uid 48); 22 Jan 2019 12:10:29 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88972] popcnt of limited 128-bit number with unnecessary zeroing
Date: Tue, 22 Jan 2019 12:10: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail 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: bug_status resolution
Message-ID: <bug-88972-4-nrT81BimNM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88972-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88972-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: 2019-01/txt/msg03065.txt.bz2
Content-length: 668

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
This is by design.

/* X86_TUNE_AVOID_FALSE_DEP_FOR_BMI: Avoid false dependency
   for bit-manipulation instructions.  */
DEF_TUNE (X86_TUNE_AVOID_FALSE_DEP_FOR_BMI, "avoid_false_dep_for_bmi",
          m_SANDYBRIDGE | m_CORE_AVX2 | m_GENERIC)
>From gcc-bugs-return-630257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:10:52 2019
Return-Path: <gcc-bugs-return-630257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21344 invoked by alias); 22 Jan 2019 12:10:51 -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 21292 invoked by uid 48); 22 Jan 2019 12:10:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 12:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88971-4-ZdMgtUPlsE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03066.txt.bz2
Content-length: 993

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> This is because it still needs to generate the std::string objects at the
> caller
> site (outside of the if (print)).  This involves quite some code to get
> rid of, and even at -O3 we do not inline basic_string::basic_string it seems
> (ISTR that is out-of-line in the library):
> 
>   __asm__ __volatile__("mfence" :  :  : "memory");
>   _6 = MEM[(const int *)&data + 4B];
>   if (_6 > 0)
>     goto <bb 3>; [41.48%]
>   else
>     goto <bb 11>; [58.52%]
> 
>   <bb 3> [local count: 445388109]:
>   std::basic_string<char>::basic_string (&D.39204, "<", &D.39205);
>   _7 = MEM[(char * *)&D.39204];
>   _8 = _7 + 18446744073709551592;
>   if (_8 != &_S_empty_rep_storage)
>     goto <bb 5>; [10.00%]
>   else
>     goto <bb 4>; [90.00%]

Looks like you're using -D_GLIBCXX_USE_CXX11_ABI=0 but the OP is not.
>From gcc-bugs-return-630258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:13:06 2019
Return-Path: <gcc-bugs-return-630258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24365 invoked by alias); 22 Jan 2019 12:13:05 -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 24289 invoked by uid 48); 22 Jan 2019 12:13:01 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88952] The asm operator modifiers for rs6000 should be documented like they are for x86
Date: Tue, 22 Jan 2019 12:13: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: 4.2.2
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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:
Message-ID: <bug-88952-4-j3zNjprpjO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88952-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: 2019-01/txt/msg03067.txt.bz2
Content-length: 447

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

--- Comment #11 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to Christopher Leonard from comment #10)
> Getting contradictory statements now:
> >reg:reg+1 maps to lo:hi on x86.
> >On x86, we don't allow register pairs in asm at all.
> 
> Not allowing, or printing a warning, is much better behavior than what I
> have been getting on PPC.

Ah, sorry - x86 emits a warning.
>From gcc-bugs-return-630259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:31:47 2019
Return-Path: <gcc-bugs-return-630259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50547 invoked by alias); 22 Jan 2019 12:31: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 50485 invoked by uid 48); 22 Jan 2019 12:31:43 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/51765] [9 Regression] Testsuite ICEs with -flto
Date: Tue, 22 Jan 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-51765-4-A3SNTHh9me@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51765-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: 2019-01/txt/msg03068.txt.bz2
Content-length: 672

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

Arseny Solokha <asolokha at gmx dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |asolokha at gmx dot com

--- Comment #9 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Jan Hubicka from comment #8)
> during IPA pass: fnsummary
> /aux/hubicka/trunk4/gcc/testsuite/g++.dg/ext/vector33.C:10:1: internal
> compiler error: tree code 'template_parm_index' is not supported in LTO
> streams

This is PR83997, which already has some problem analysis by Jakub.
>From gcc-bugs-return-630260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:32:00 2019
Return-Path: <gcc-bugs-return-630260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51350 invoked by alias); 22 Jan 2019 12:32:00 -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 51248 invoked by uid 48); 22 Jan 2019 12:31:53 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88968] [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-88968-4-mtrVFAro8k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg03069.txt.bz2
Content-length: 2928

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

Arseny Solokha <asolokha at gmx dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c                           |middle-end

--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> ---
struct {
  unsigned int hq : 16;
  unsigned int dv : 1;
} __attribute__ ((__packed__)) e2;

int
yp (void)
{
  int sr;

#pragma omp atomic capture
  {
    sr = e2.hq;
    e2.hq = 0;
  }

  return sr;
}

% gcc-9.0.0-alpha20190120 -fopenmp -c zto53g7w.c
zto53g7w.c: In function 'yp':
zto53g7w.c:15:3: internal compiler error: in fold_convert_loc, at
fold-const.c:2552
   15 |   }
      |   ^
0x615112 fold_convert_loc(unsigned int, tree_node*, tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/fold-const.c:2552
0xa741b8 omit_one_operand_loc(unsigned int, tree_node*, tree_node*, tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/fold-const.c:3769
0x8918ad c_finish_omp_atomic(unsigned int, tree_code, tree_code, tree_node*,
tree_node*, tree_node*, tree_node*, tree_node*, bool, omp_memory_order, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-omp.c:412
0x834307 c_parser_omp_atomic
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:16470
0x843aea c_parser_omp_construct
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:19490
0x821667 c_parser_pragma
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:11562
0x83b2b4 c_parser_compound_statement_nostart
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:5114
0x83b8b8 c_parser_compound_statement
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:4980
0x83d1b5 c_parser_declaration_or_fndef
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:2352
0x84456f c_parser_external_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:1653
0x844fb1 c_parser_translation_unit
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:1534
0x844fb1 c_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:19840
0x898bcb c_common_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-opts.c:1155
>From gcc-bugs-return-630261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:36:45 2019
Return-Path: <gcc-bugs-return-630261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62473 invoked by alias); 22 Jan 2019 12:36:45 -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 62400 invoked by uid 48); 22 Jan 2019 12:36:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 12:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88971-4-HQ5EKkJAkK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03070.txt.bz2
Content-length: 1909

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to Richard Biener from comment #1)
> > This is because it still needs to generate the std::string objects at the
> > caller
> > site (outside of the if (print)).  This involves quite some code to get
> > rid of, and even at -O3 we do not inline basic_string::basic_string it seems
> > (ISTR that is out-of-line in the library):
> > 
> >   __asm__ __volatile__("mfence" :  :  : "memory");
> >   _6 = MEM[(const int *)&data + 4B];
> >   if (_6 > 0)
> >     goto <bb 3>; [41.48%]
> >   else
> >     goto <bb 11>; [58.52%]
> > 
> >   <bb 3> [local count: 445388109]:
> >   std::basic_string<char>::basic_string (&D.39204, "<", &D.39205);
> >   _7 = MEM[(char * *)&D.39204];
> >   _8 = _7 + 18446744073709551592;
> >   if (_8 != &_S_empty_rep_storage)
> >     goto <bb 5>; [10.00%]
> >   else
> >     goto <bb 4>; [90.00%]
> 
> Looks like you're using -D_GLIBCXX_USE_CXX11_ABI=0 but the OP is not.

Indeed.  It's still missed inlining that makes elding of the argument
construction difficult.  Looks like

std::__cxx11::basic_string<char>::_M_construct<const char*>

is not marked inline (so needs -finline-functions to get IPA inlining
processing).  Indeed I see

      // For forward_iterators up to random_access_iterators, used for
      // string::iterator, _CharT*, etc.
      template<typename _FwdIterator>
        void
        _M_construct(_FwdIterator __beg, _FwdIterator __end,
                     std::forward_iterator_tag);

and others.
>From gcc-bugs-return-630262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:42:50 2019
Return-Path: <gcc-bugs-return-630262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72048 invoked by alias); 22 Jan 2019 12:42:49 -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 71971 invoked by uid 48); 22 Jan 2019 12:42:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88968] [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 12:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88968-4-0kJcFyIn3T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg03071.txt.bz2
Content-length: 2048

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The problem is that for these packed structs the DECL_BIT_FIELD_REPRESENTATIVE
is not integral FIELD_DECL that the c-omp.c code assumes.  BIT_FIELD_REF seems
to work with non-integral base types from which the field is extracted:
/* Reference to a group of bits within an object.  Similar to COMPONENT_REF
   except the position is given explicitly rather than via a FIELD_DECL.
   Operand 0 is the structure or union expression;
   operand 1 is a tree giving the constant number of bits being referenced;
   operand 2 is a tree giving the constant position of the first referenced
bit.
   The result type width has to match the number of bits referenced.
   If the result type is integral, its signedness specifies how it is extended
   to its mode width.  */
DEFTREECODE (BIT_FIELD_REF, "bit_field_ref", tcc_reference, 3)
but we need to insert the field back and for that the BIT_INSERT_EXPR we are
using requires that it stores into an integral or vector type expression:
/* Given a container value, a replacement value and a bit position within
   the container, produce the value that results from replacing the part of
   the container starting at the bit position with the replacement value.
   Operand 0 is a tree for the container value of integral or vector type;
   Operand 1 is a tree for the replacement value of another integral or
   the vector element type;
   Operand 2 is a tree giving the constant bit position;
   The number of bits replaced is given by the precision of the type of the
   replacement value if it is integral or by its size if it is non-integral.
   ???  The reason to make the size of the replacement implicit is to avoid
   introducing a quaternary operation.
   The replaced bits shall be fully inside the container.  If the container
   is of vector type, then these bits shall be aligned with its elements.  */
DEFTREECODE (BIT_INSERT_EXPR, "bit_insert_expr", tcc_expression, 3)
>From gcc-bugs-return-630263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:49:59 2019
Return-Path: <gcc-bugs-return-630263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113954 invoked by alias); 22 Jan 2019 12:49:57 -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 113483 invoked by uid 48); 22 Jan 2019 12:49:53 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88974] New: [9 Regression] ICE: Segmentation fault (in linemap_resolve_location)
Date: Tue, 22 Jan 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88974-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: 2019-01/txt/msg03072.txt.bz2
Content-length: 4584

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

            Bug ID: 88974
           Summary: [9 Regression] ICE: Segmentation fault (in
                    linemap_resolve_location)
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: error-recovery, ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: preprocessor
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gcc-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
snippet derived from test/Frontend/rewrite-includes-invalid-hasinclude.c from
the clang 7.0.1 testsuite:

#if __has_include__ (<bar.h)
#endif

% MALLOC_PERTURB_=1 MALLOC_CHECK_=3 gcc-9.0.0-alpha20190120 -c ruc8wen6.c
ruc8wen6.c:1:29: error: missing terminating > character
    1 | #if __has_include__ (<bar.h)
      |                             ^

ruc8wen6.c:1: internal compiler error: Segmentation fault
    1 | #if __has_include__ (<bar.h)
      | 
0xd701df crash_signal
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/toplev.c:326
0x17202bb linemap_resolve_location(line_maps*, unsigned int,
location_resolution_kind, line_map_ordinary const**)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/line-map.c:1540
0x16e6c21 diagnostic_report_current_module(diagnostic_context*, unsigned int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/diagnostic.c:598
0xdcd3a1 diagnostic_report_current_function(diagnostic_context*,
diagnostic_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-diagnostic.c:39
0xdcd400 default_tree_diagnostic_starter
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-diagnostic.c:48
0x16e5697 diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/diagnostic.c:1016
0x87a3ea c_cpp_diagnostic(cpp_reader*, cpp_diagnostic_level,
cpp_warning_reason, rich_location*, char const*, __va_list_tag (*) [1])
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-common.c:6318
0x17114fc cpp_diagnostic
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/errors.c:75
0x17116ee cpp_error(cpp_reader*, cpp_diagnostic_level, char const*, ...)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/errors.c:89
0x1712955 parse_has_include
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/expr.c:2242
0x1716058 eval_token
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/expr.c:1159
0x1716058 _cpp_parse_expr
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/expr.c:1328
0x170dd61 do_if
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/directives.c:2008
0x170f5b0 _cpp_handle_directive
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/directives.c:543
0x171e664 _cpp_lex_token
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/lex.c:2609
0x17264c7 cpp_get_token_1
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/libcpp/macro.c:2703
0x88f241 c_lex_with_flags(tree_node**, unsigned int*, unsigned char*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-lex.c:405
0x8189c0 c_lex_one_token
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:249
0x844e6d c_parser_peek_token(c_parser*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:436
0x844e6d c_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c/c-parser.c:19828

I suspect the issue is GC-related but I've failed to find a way to expose it w/
Valgrind or using small ggc-min-* parameters, so glibc-based environment is
necessary to reproduce it for now.
>From gcc-bugs-return-630265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:50:14 2019
Return-Path: <gcc-bugs-return-630265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116359 invoked by alias); 22 Jan 2019 12:50:13 -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 115322 invoked by uid 48); 22 Jan 2019 12:50:09 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88976] New: ICE in fold_convert_loc, at fold-const.c:2552
Date: Tue, 22 Jan 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88976-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: 2019-01/txt/msg03074.txt.bz2
Content-length: 4119

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

            Bug ID: 88976
           Summary: ICE in fold_convert_loc, at fold-const.c:2552
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, openmp
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107), 8.2, 7.4, 6.3, 5.5, 4.9.4 all ICE
when compiling the following snippet w/ -fopenmp:

template <class T> void
jm (T cv)
{
#pragma omp cancel parallel if (cv)
}

% g++-9.0.0-alpha20190120 -fopenmp -c icjm7wqb.cpp
icjm7wqb.cpp: In function 'void jm(T)':
icjm7wqb.cpp:4:36: internal compiler error: in fold_convert_loc, at
fold-const.c:2552
    4 | #pragma omp cancel parallel if (cv)
      |                                    ^
0x6d8408 fold_convert_loc(unsigned int, tree_node*, tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/fold-const.c:2552
0xa307b1 finish_omp_cancel(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/semantics.c:9060
0x997e65 cp_parser_omp_cancel
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:37755
0x997e65 cp_parser_pragma
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:40735
0x9a00ec cp_parser_statement
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11204
0x9a0c38 cp_parser_statement_seq_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11592
0x9a0d18 cp_parser_compound_statement
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:11546
0x9bab16 cp_parser_function_body
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:22530
0x9bab16 cp_parser_ctor_initializer_opt_and_function_body
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:22567
0x9bb3f0 cp_parser_function_definition_after_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27630
0x9bc1d4 cp_parser_function_definition_from_specifiers_and_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27546
0x9bc1d4 cp_parser_init_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:20205
0x9bf7a4 cp_parser_single_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:28096
0x9bf90d cp_parser_template_declaration_after_parameters
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27688
0x9c026e cp_parser_explicit_template_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27934
0x9c026e cp_parser_template_declaration_after_export
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27953
0x9c2e09 cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13122
0x9c346e cp_parser_translation_unit
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:4698
0x9c346e c_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:41003
0xacce0b c_common_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-opts.c:1155
>From gcc-bugs-return-630264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:50:04 2019
Return-Path: <gcc-bugs-return-630264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114632 invoked by alias); 22 Jan 2019 12:50:03 -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 113971 invoked by uid 48); 22 Jan 2019 12:49:58 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88975] New: ICE: Segmentation fault (in verify_ssa or gimple_code)
Date: Tue, 22 Jan 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88975-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: 2019-01/txt/msg03073.txt.bz2
Content-length: 3102

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

            Bug ID: 88975
           Summary: ICE: Segmentation fault (in verify_ssa or gimple_code)
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, openmp
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

1.

gcc-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
snippet w/ -fopenmp -fchecking:

void
mr (int gy)
{
  int ij[gy];
  int sk;

#pragma omp taskloop reduction(+:ij)
  for (sk = 0; sk < 1; ++sk)
    {
    }
}

% gcc-9.0.0-alpha20190120 -fopenmp -c xsihfn9u.c
during GIMPLE pass: ssa
xsihfn9u.c: In function 'mr':
xsihfn9u.c:11:1: internal compiler error: Segmentation fault
   11 | }
      | ^
0xd701df crash_signal
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/toplev.c:326
0xf923dc verify_ssa(bool, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-ssa.c:1050
0xc89d0d execute_function_todo
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:1984
0xc8ab0e execute_todo
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:2031

2.

Compiling the above snippet w/ -fopenmp -fno-checking yields the following
instead:

% gcc-9.0.0-alpha20190120 -fopenmp -fno-checking -c xsihfn9u.c
during RTL pass: expand
xsihfn9u.c: In function 'mr':
xsihfn9u.c:2:1: internal compiler error: Segmentation fault
    2 | mr (int gy)
      | ^~
0xd701df crash_signal
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/toplev.c:326
0xf8db84 gimple_code
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple.h:1689
0xf8db84 gimple_nop_p
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple.h:6466
0xf8db84 ssa_undefined_value_p(tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-ssa.c:1295
0xf8db84 ssa_undefined_value_p(tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-ssa.c:1286
0xe218df get_undefined_value_partitions
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-outof-ssa.c:978
0xe218df remove_ssa_form
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-outof-ssa.c:1072
0xe218df rewrite_out_of_ssa(ssaexpand*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-outof-ssa.c:1306
0x912660 execute
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cfgexpand.c:6314
>From gcc-bugs-return-630266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 12:52:30 2019
Return-Path: <gcc-bugs-return-630266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119390 invoked by alias); 22 Jan 2019 12:52:30 -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 119314 invoked by uid 48); 22 Jan 2019 12:52:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Tue, 22 Jan 2019 12:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88936-4-l2Z4r48uSA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg03075.txt.bz2
Content-length: 884

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

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #7)
> Hi,
> there is ipa_reduced_postorder that will compute SCCs and store scc
> index.

OK, from looking at examples it seems that I can access node->aux
as ipa_dfs_info * after ipa_reduced_postorder and before I call
ipa_free_postorder_info.  To check whether a call is possibly
recursing to the caller I'd then check whether the callers and the
callees DFS number match.  That works as far as direct calls are
considered - but what about indirect calls?

Not that I'm sure what to do when hitting a possibly recursive call - dropping
all the way to pt_anything for arguments would be a bit harsh.  But whether
ensuring that we do not end up with a singleton composed of caller automatic
vars is enough I'm not sure...
>From gcc-bugs-return-630267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 13:10:18 2019
Return-Path: <gcc-bugs-return-630267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37670 invoked by alias); 22 Jan 2019 13:10:17 -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 37590 invoked by uid 48); 22 Jan 2019 13:10:13 -0000
From: "maratrus at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 13:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: maratrus at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88971-4-07puOOrgZb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03076.txt.bz2
Content-length: 873

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

--- Comment #5 from Marat Stanichenko <maratrus at mail dot ru> ---

(In reply to Richard Biener from comment #1)
> This is because it still needs to generate the std::string objects at the
> caller

Thank you very much for the comment! That is probably why I had to add another
string parameter to the function `PrintBad` in the example provided to trigger
this behaviour. The fact is that in the production environment where I managed
to spot this, the compiler could not optimize the function that is very similar
to `PrintGood` and has just a single string parameter. I didn't manage to
reproduce it when simplifying things while preparing a test-case here.

Do you believe that compiler can do better in such situations? Or the current
behaviour is perfectly valid and no improvements are really needed?
>From gcc-bugs-return-630268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 13:14:37 2019
Return-Path: <gcc-bugs-return-630268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49453 invoked by alias); 22 Jan 2019 13:14:35 -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 49392 invoked by uid 48); 22 Jan 2019 13:14:32 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88977] New: __builtin_is_constant_evaluated() as function template argument causes substitution failure
Date: Tue, 22 Jan 2019 13:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88977-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: 2019-01/txt/msg03077.txt.bz2
Content-length: 1150

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

            Bug ID: 88977
           Summary: __builtin_is_constant_evaluated() as function template
                    argument causes substitution failure
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ensadc at mailnesia dot com
  Target Milestone: ---

https://wandbox.org/permlink/LYuJZ4w7YLgidqdi

====
template<bool> int f();

int x = f<__builtin_is_constant_evaluated()>();

====
prog.cc:3:46: error: no matching function for call to
'f<__builtin_is_constant_evaluated()>()'
    3 | int x = f<__builtin_is_constant_evaluated()>();
      |                                              ^
prog.cc:1:20: note: candidate: 'template<bool <anonymous> > int f()'
    1 | template<bool> int f();
      |                    ^
prog.cc:1:20: note:   template argument deduction/substitution failed:
====

It works fine with class/variable/alias templates.
>From gcc-bugs-return-630269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 13:43:34 2019
Return-Path: <gcc-bugs-return-630269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24541 invoked by alias); 22 Jan 2019 13:43:34 -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 23177 invoked by uid 48); 22 Jan 2019 13:43:28 -0000
From: "patrickdepinguin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88240] Potential optimization bug: invalid pre-load of floating-point value could cause SIGFPE-underflow if value is integer
Date: Tue, 22 Jan 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: patrickdepinguin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88240-4-vHpq1tSzc9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88240-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: 2019-01/txt/msg03078.txt.bz2
Content-length: 249

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

--- Comment #11 from Thomas De Schampheleire <patrickdepinguin at gmail dot com> ---
Any feedback? With the reduced testcase qemu is out of the picture.
Do you agree that this is a bug in gcc?
>From gcc-bugs-return-630270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 13:46:01 2019
Return-Path: <gcc-bugs-return-630270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39385 invoked by alias); 22 Jan 2019 13:46:00 -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 36781 invoked by uid 48); 22 Jan 2019 13:45:46 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88948] [9 Regression] ICE in elimination_costs_in_insn, at reload1.c:3640 since r264148
Date: Tue, 22 Jan 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88948-4-XjIVa62n08@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88948-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: 2019-01/txt/msg03079.txt.bz2
Content-length: 237

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

--- Comment #3 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Created attachment 45494
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45494&action=edit
Proposed patch
>From gcc-bugs-return-630271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 13:49:51 2019
Return-Path: <gcc-bugs-return-630271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90218 invoked by alias); 22 Jan 2019 13:49: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 90081 invoked by uid 48); 22 Jan 2019 13:49:45 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86214] [8 Regression] Strongly increased stack usage
Date: Tue, 22 Jan 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86214-4-SnhFWWjcrC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86214-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: 2019-01/txt/msg03080.txt.bz2
Content-length: 5941

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

Christophe Lyon <clyon at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clyon at gcc dot gnu.org

--- Comment #20 from Christophe Lyon <clyon at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #17)
> Author: jakub
> Date: Fri Jan 18 10:07:27 2019
> New Revision: 268067
> 
> URL: https://gcc.gnu.org/viewcvs?rev=268067&root=gcc&view=rev
> Log:
> 	PR tree-optimization/86214
> 	* tree-inline.h (struct copy_body_data): Add
> 	add_clobbers_to_eh_landing_pads member.
> 	* tree-inline.c (add_clobbers_to_eh_landing_pad): New function.
> 	(copy_edges_for_bb): Call it if EH edge destination is <
> 	id->add_clobbers_to_eh_landing_pads.  Fix a comment typo.
> 	(expand_call_inline): Set id->add_clobbers_to_eh_landing_pads
> 	if flag_stack_reuse != SR_NONE and clear it afterwards.
> 
> 	* g++.dg/opt/pr86214-1.C: New test.
> 	* g++.dg/opt/pr86214-2.C: New test.
> 
> Added:
>     trunk/gcc/testsuite/g++.dg/opt/pr86214-1.C
>     trunk/gcc/testsuite/g++.dg/opt/pr86214-2.C
> Modified:
>     trunk/gcc/ChangeLog
>     trunk/gcc/testsuite/ChangeLog
>     trunk/gcc/tree-inline.c
>     trunk/gcc/tree-inline.h

Hi Jakub,

Since you committed this patch, I've noticed regressions on some arm targets:
FAIL: 23_containers/list/requirements/exception/basic.cc execution test
libstdc++.log has this:
spawn [open ...]
N10__gnu_test12functor_base19iterator_operationsINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEEEE
end count 2
N10__gnu_test12functor_base25const_iterator_operationsINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEEEE
end count 3
N10__gnu_test12functor_base11erase_pointINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1ELb0EEE
end count 4
N10__gnu_test12functor_base11erase_rangeINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1ELb0EEE
end count 5
N10__gnu_test12functor_base12insert_pointINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1ELb0EEE
end count 6
N10__gnu_test12functor_base7emplaceINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb0EEE
end count 7
N10__gnu_test12functor_base13emplace_pointINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1ELb0ELb0EEE
end count 8
N10__gnu_test12functor_base13emplace_frontINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1EEE
end count 9
N10__gnu_test12functor_base12emplace_backINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1EEE
end count 10
N10__gnu_test12functor_base9pop_frontINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1EEE
end count 11
N10__gnu_test12functor_base8pop_backINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1EEE
end count 12
N10__gnu_test12functor_base10push_frontINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1EEE
end count 13
N10__gnu_test12functor_base9push_backINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb1EEE
end count 14
N10__gnu_test12functor_base6rehashINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEELb0EEE
end count 15
N10__gnu_test12functor_base4swapINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS4_21throw_allocator_limitIS5_EEEEEE
end count 16
qemu: uncaught target signal 11 (Segmentation fault) - core dumped

The qemu trace does not seem very helpful (and is probably incomplete):
IN:
_ZN10__gnu_test12basic_safetyINSt7__cxx114listIN9__gnu_cxx17throw_value_limitENS3_21throw_allocator_limitIS4_EEEEE3runEv
0x0001c724:  e5943008  ldr      r3, [r4, #8]
0x0001c728:  e59d2010  ldr      r2, [sp, #0x10]
0x0001c72c:  e59d101c  ldr      r1, [sp, #0x1c]
0x0001c730:  e3530000  cmp      r3, #0
0x0001c734:  e5987000  ldr      r7, [r8]
0x0001c738:  e5812000  str      r2, [r1]
0x0001c73c:  e5896000  str      r6, [sb]
0x0001c740:  e5882000  str      r2, [r8]
0x0001c744:  0a000510  beq      #0x1db8c

----------------
IN: 
0x40adc6bc:  e0849009  add      sb, r4, sb
0x40adc6c0:  e59f29c8  ldr      r2, [pc, #0x9c8]
0x40adc6c4:  e5993004  ldr      r3, [sb, #4]
0x40adc6c8:  e08f2002  add      r2, pc, r2
0x40adc6cc:  e3833001  orr      r3, r3, #1
0x40adc6d0:  e1550002  cmp      r5, r2
0x40adc6d4:  e59da018  ldr      sl, [sp, #0x18]
0x40adc6d8:  e5893004  str      r3, [sb, #4]
0x40adc6dc:  0a000002  beq      #0x40adc6ec

----------------
IN: 
0x40adc6ec:  e59f39a0  ldr      r3, [pc, #0x9a0]
0x40adc6f0:  e2846008  add      r6, r4, #8
0x40adc6f4:  e08f3003  add      r3, pc, r3
0x40adc6f8:  e593102c  ldr      r1, [r3, #0x2c]
0x40adc6fc:  e3510000  cmp      r1, #0
0x40adc700:  1affff13  bne      #0x40adc354

----------------
IN: 
0x40adc704:  e1a00006  mov      r0, r6
0x40adc708:  e28dd044  add      sp, sp, #0x44
0x40adc70c:  e8bd8ff0  pop      {r4, r5, r6, r7, r8, sb, sl, fp, pc}

----------------
IN: 
0x40adc6ac:  e085240c  add      r2, r5, ip, lsl #8
0x40adc6b0:  e2822028  add      r2, r2, #0x28
0x40adc6b4:  e3a03001  mov      r3, #1
0x40adc6b8:  eaffffce  b        #0x40adc5f8


I've noticed this on:
arm-none-linux-gnueabihf
--with-mode arm
--with-cpu cortex-a9
--with-fpu vfp
RUNTESTFLAGS: -march=armv5t

arm-none-linux-gnueabihf
--with-mode arm
--with-cpu arm10tdmi
--with-fpu vfp

arm-none-linux-gnueabihf
--with-mode arm
--with-cpu cortex-a5
--with-fpu vfpv3-d16-fp16

armeb-none-linux-gnueabihf
--with-mode arm
--with-cpu cortex-a9
--with-fpu vfpv3-d16-fp16

Other arm-none-linux-gnueabihf configs I test still run fine.
>From gcc-bugs-return-630272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:01:19 2019
Return-Path: <gcc-bugs-return-630272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100708 invoked by alias); 22 Jan 2019 14:01:06 -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 100630 invoked by uid 48); 22 Jan 2019 14:01:02 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Tue, 22 Jan 2019 14:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88044-4-gxcfBCbrTS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-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: 2019-01/txt/msg03081.txt.bz2
Content-length: 240

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

--- Comment #17 from Christophe Lyon <clyon at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #16)
> Fixed.

I confirm the problem I mentioned in #c3 is now fixed. Thanks!
>From gcc-bugs-return-630273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:02:12 2019
Return-Path: <gcc-bugs-return-630273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102300 invoked by alias); 22 Jan 2019 14:02:11 -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 102181 invoked by uid 48); 22 Jan 2019 14:02:02 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88919] New test case gcc.dg/vect/pr88903-1.c in r268076 fails
Date: Tue, 22 Jan 2019 14:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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-88919-4-YHyTaAQsTR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88919-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: 2019-01/txt/msg03082.txt.bz2
Content-length: 581

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

Christophe Lyon <clyon at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clyon at gcc dot gnu.org

--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Sandra posted a patch that will probably fix this (out-of-bound shift
> values).

Do you mean https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01207.html ?
>From gcc-bugs-return-630274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:02:21 2019
Return-Path: <gcc-bugs-return-630274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103083 invoked by alias); 22 Jan 2019 14:02: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 102695 invoked by uid 48); 22 Jan 2019 14:02:15 -0000
From: "anton at samba dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 14:02: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anton at samba dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88965-4-6NRhbQKla4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg03083.txt.bz2
Content-length: 245

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

--- Comment #5 from Anton Blanchard <anton at samba dot org> ---
Martin: "gcc -c x.c" was enough to hit it on a build of trunk on my POWER9
ppc64le box.

Jakub: Thanks, that fixes it for me.
>From gcc-bugs-return-630275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:04:01 2019
Return-Path: <gcc-bugs-return-630275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105356 invoked by alias); 22 Jan 2019 14:04:00 -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 105323 invoked by uid 55); 22 Jan 2019 14:03:55 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88469] [7/8/9 regression] AAPCS - Struct with 64-bit bitfield may be passed in wrong registers
Date: Tue, 22 Jan 2019 14:04: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: 8.2.0
X-Bugzilla-Keywords: ABI, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88469-4-14E9CyJ1vy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88469-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88469-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: 2019-01/txt/msg03084.txt.bz2
Content-length: 2149

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

--- Comment #6 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Tue Jan 22 14:03:22 2019
New Revision: 268151

URL: https://gcc.gnu.org/viewcvs?rev=268151&root=gcc&view=rev
Log:
[arm] PR target/88469 fix incorrect argument passing with 64-bit bitfields

Unfortunately another PCS bug has come to light with the layout of
structs whose alignment is dominated by a 64-bit bitfield element.
Such fields in the type list appear to have alignment 1, but in
reality, for the purposes of alignment of the underlying structure,
the alignment is derived from the underlying bitfield's type.  We've
been getting this wrong since support for over-aligned record types
was added several releases back.  Worse still, the existing code may
generate unaligned memory accesses that may fault on some versions of
the architecture.

I've taken the opportunity to add a few more tests that check the
passing arguments with overalignment in the PCS.  Looking through the
existing tests it looked like they were really only checking
self-consistency and not the precise location of the arguments.

PR target/88469

gcc:
        * config/arm/arm.c (arm_needs_doubleword_align): Return 2 if a record's
        alignment is dominated by a bitfield with 64-bit aligned base type.
        (arm_function_arg): Emit a warning if the alignment has changed since
        earlier GCC releases.
        (arm_function_arg_boundary): Likewise.
        (arm_setup_incoming_varargs): Likewise.

gcc/testsuite:
        * gcc.target/arm/aapcs/bitfield1.c: New test.
        * gcc.target/arm/aapcs/overalign_rec1.c: New test.
        * gcc.target/arm/aapcs/overalign_rec2.c: New test.
        * gcc.target/arm/aapcs/overalign_rec3.c: New test.

Added:
    trunk/gcc/testsuite/gcc.target/arm/aapcs/bitfield1.c
    trunk/gcc/testsuite/gcc.target/arm/aapcs/overalign_rec1.c
    trunk/gcc/testsuite/gcc.target/arm/aapcs/overalign_rec2.c
    trunk/gcc/testsuite/gcc.target/arm/aapcs/overalign_rec3.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/arm/arm.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:08:16 2019
Return-Path: <gcc-bugs-return-630276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56632 invoked by alias); 22 Jan 2019 14:08:15 -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 56482 invoked by uid 48); 22 Jan 2019 14:08:07 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 22 Jan 2019 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov 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:
Message-ID: <bug-88398-4-T7IYrEYokQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-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: 2019-01/txt/msg03085.txt.bz2
Content-length: 668

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

--- Comment #21 from ktkachov at gcc dot gnu.org ---
So the actual hot loop in xz_r does:
typedef unsigned char __uint8_t;
typedef unsigned int __uint32_t;
typedef unsigned long long __uint64_t;

int
foo (const __uint64_t len_limit, const __uint8_t *cur,
             __uint32_t delta, int len) {

  const __uint8_t *pb = cur - delta;

  while (++len != len_limit) {
    if (pb[len] != cur[len])
      break;
  }

  return len;
}

The 'pb' pointer is the 'cur' pointer but moved back by 'delta'.
Presumably that means that all memory between 'pb' and 'delta' and could be
read in as wide a load as possible?
>From gcc-bugs-return-630277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:11:42 2019
Return-Path: <gcc-bugs-return-630277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119288 invoked by alias); 22 Jan 2019 14:11:41 -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 115469 invoked by uid 48); 22 Jan 2019 14:11:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88936] [7/8/9 Regression] -fipa-pta breaks bash (incorrect optimisation of recursive static function)
Date: Tue, 22 Jan 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88936-4-tfKvBOcMy8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88936-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: 2019-01/txt/msg03086.txt.bz2
Content-length: 824

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

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the idea for the fix is to make locals that escape through recursive edges
behave as if they were really *ptr with ptr pointing to &local, &localp
where localp would be "the other locals".  This could be done on the
constraint level.

Semantically equivalent is doing the above by post-processing the points-to
sets after propagation and replacing 'local' with 'local + localp'.  We'd need
to gather a bitmap of candidate UIDs for this which we could eventually
prune by the set of vars that do not escape through such an edge
(implementation
is not entirely clear).

What is missing right now is a conservative predicate telling us whether
defined function X is reachable recursively.  Honza?
>From gcc-bugs-return-630278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:14:26 2019
Return-Path: <gcc-bugs-return-630278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113970 invoked by alias); 22 Jan 2019 14:14:25 -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 113889 invoked by uid 55); 22 Jan 2019 14:14:20 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 14:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88971-4-iOk0dIaXVy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03087.txt.bz2
Content-length: 1287

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

--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, maratrus at mail dot ru wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88971
> 
> --- Comment #5 from Marat Stanichenko <maratrus at mail dot ru> ---
> 
> (In reply to Richard Biener from comment #1)
> > This is because it still needs to generate the std::string objects at the
> > caller
> 
> Thank you very much for the comment! That is probably why I had to add another
> string parameter to the function `PrintBad` in the example provided to trigger
> this behaviour. The fact is that in the production environment where I managed
> to spot this, the compiler could not optimize the function that is very similar
> to `PrintGood` and has just a single string parameter. I didn't manage to
> reproduce it when simplifying things while preparing a test-case here.
> 
> Do you believe that compiler can do better in such situations? Or the current
> behaviour is perfectly valid and no improvements are really needed?

The compiler can of course do better when estimating the benefit of
inlining.  It's just not entirely clear if it is reasonably easy to
do so ... [let aside the -finline-function issue]
>From gcc-bugs-return-630280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:16:45 2019
Return-Path: <gcc-bugs-return-630280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116981 invoked by alias); 22 Jan 2019 14:16:44 -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 116871 invoked by uid 55); 22 Jan 2019 14:16:41 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 22 Jan 2019 14:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
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:
Message-ID: <bug-88398-4-nTGhVulhwA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-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: 2019-01/txt/msg03089.txt.bz2
Content-length: 1043

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

--- Comment #22 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, ktkachov at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
> 
> --- Comment #21 from ktkachov at gcc dot gnu.org ---
> So the actual hot loop in xz_r does:
> typedef unsigned char __uint8_t;
> typedef unsigned int __uint32_t;
> typedef unsigned long long __uint64_t;
> 
> int
> foo (const __uint64_t len_limit, const __uint8_t *cur,
>              __uint32_t delta, int len) {
> 
>   const __uint8_t *pb = cur - delta;
> 
>   while (++len != len_limit) {
>     if (pb[len] != cur[len])
>       break;
>   }
> 
>   return len;
> }
> 
> The 'pb' pointer is the 'cur' pointer but moved back by 'delta'.
> Presumably that means that all memory between 'pb' and 'delta' and could be
> read in as wide a load as possible?

A C language lawyer would agree with that.  But does it really help?
The loop also accesses [cur + len, cur + len_limit].
>From gcc-bugs-return-630279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:16:31 2019
Return-Path: <gcc-bugs-return-630279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116131 invoked by alias); 22 Jan 2019 14:16:30 -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 116022 invoked by uid 48); 22 Jan 2019 14:16:19 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88469] [7/8 regression] AAPCS - Struct with 64-bit bitfield may be passed in wrong registers
Date: Tue, 22 Jan 2019 14:16: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: 8.2.0
X-Bugzilla-Keywords: ABI, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88469-4-p5uJ5Vmrt9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88469-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88469-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: 2019-01/txt/msg03088.txt.bz2
Content-length: 700

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

Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[7/8/9 regression] AAPCS -  |[7/8 regression] AAPCS -
                   |Struct with 64-bit bitfield |Struct with 64-bit bitfield
                   |may be passed in wrong      |may be passed in wrong
                   |registers                   |registers

--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Fixed on trunk.  Still need mitigation for gcc-7/8 and to deal with
boostrapping gcc-9 with gcc-6/7/8.
>From gcc-bugs-return-630281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:17:33 2019
Return-Path: <gcc-bugs-return-630281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1178 invoked by alias); 22 Jan 2019 14:17:33 -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 130793 invoked by uid 55); 22 Jan 2019 14:17:28 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88919] New test case gcc.dg/vect/pr88903-1.c in r268076 fails
Date: Tue, 22 Jan 2019 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: WAITING
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:
Message-ID: <bug-88919-4-c4cyPVRaFC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88919-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: 2019-01/txt/msg03090.txt.bz2
Content-length: 809

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

--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, clyon at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88919
> 
> Christophe Lyon <clyon at gcc dot gnu.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |clyon at gcc dot gnu.org
> 
> --- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #2)
> > Sandra posted a patch that will probably fix this (out-of-bound shift
> > values).
> 
> Do you mean https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01207.html ?

Yes.
>From gcc-bugs-return-630282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:18:26 2019
Return-Path: <gcc-bugs-return-630282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2455 invoked by alias); 22 Jan 2019 14:18:26 -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 2351 invoked by uid 48); 22 Jan 2019 14:18:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88240] Potential optimization bug: invalid pre-load of floating-point value could cause SIGFPE-underflow if value is integer
Date: Tue, 22 Jan 2019 14:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88240-4-cWliVX0D7w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88240-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: 2019-01/txt/msg03091.txt.bz2
Content-length: 725

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-22
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yes, IMHO the bug is valid.  I've ment to assign myself (though don't hold your
breath for a fix).
>From gcc-bugs-return-630283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:28:46 2019
Return-Path: <gcc-bugs-return-630283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60730 invoked by alias); 22 Jan 2019 14:28: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 60666 invoked by uid 48); 22 Jan 2019 14:28:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88978] New: Failed outer loop vectorization with grouped accesses
Date: Tue, 22 Jan 2019 14:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88978-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: 2019-01/txt/msg03092.txt.bz2
Content-length: 1731

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

            Bug ID: 88978
           Summary: Failed outer loop vectorization with grouped accesses
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

We fail to vectorize outer loops when there are grouped accesses in the
inner loop:

int a[1024];
int b[1024][1024];

void foo ()
{
  for (int i = 0; i < 512; ++i)
    {
      int a1 = a[2*i];
      int a2 = a[2*i+1];
      for (int j = 0; j < 1024; ++j)
        {
          b[j][2*i] = a1;
          b[j][2*i+1] = a2;
        }
    }
}

This is mostly because we cannot do SLP here (for implementation reasons).
We are vectorizing the following just fine, applying interleaving to the
outer loop accesses:

int a[1024];
int b[1024][1024];

void foo ()
{
  for (int i = 0; i < 512; ++i)
    {
      int a1 = a[2*i];
      int a2 = a[2*i+1];
      for (int j = 0; j < 1024; ++j)
        b[j][i] = a1+a2;
    }
}

The guard in question is the following which is premature (before SLP
would be even tried) and somewhat inaccurate since it is grouped
accesses in the inner loop when doing outer loop vectorization rather
than grouped accesses in an outer loop that fail.

static bool
vect_analyze_data_ref_access (dr_vec_info *dr_info)
{
...
  if (loop && nested_in_vect_loop_p (loop, stmt_info))
    {
      if (dump_enabled_p ())
        dump_printf_loc (MSG_NOTE, vect_location,
                         "grouped access in outer loop.\n");
      return false;
    }
>From gcc-bugs-return-630284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:29:03 2019
Return-Path: <gcc-bugs-return-630284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61681 invoked by alias); 22 Jan 2019 14:29:03 -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 61607 invoked by uid 48); 22 Jan 2019 14:28:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88978] Failed outer loop vectorization with grouped accesses
Date: Tue, 22 Jan 2019 14:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88978-4-TE105DWFZh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88978-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88978-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: 2019-01/txt/msg03093.txt.bz2
Content-length: 638

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-22
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-630285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:35:09 2019
Return-Path: <gcc-bugs-return-630285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76693 invoked by alias); 22 Jan 2019 14:35:08 -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 76643 invoked by uid 48); 22 Jan 2019 14:35:04 -0000
From: "19Sebastian95 at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88979] New: [C++20] P0634R3 not working for constructor parameter types
Date: Tue, 22 Jan 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 19Sebastian95 at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88979-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: 2019-01/txt/msg03094.txt.bz2
Content-length: 1542

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

            Bug ID: 88979
           Summary: [C++20] P0634R3 not working for constructor parameter
                    types
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: 19Sebastian95 at gmx dot de
  Target Milestone: ---

# gcc -v
Using built-in specs.
COLLECT_GCC=/opt/bin/gcc
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/opt/ --enable-languages=c,c++
Thread model: posix
gcc version 9.0.0 20190118 (experimental) (GCC) 

# Description: 
When compiling the following code and uncommenting the first constructor of A
it'll throw the error in the comment. 
The expected behaviour would either be "error: need 'typename' before 'T::type'
because 'T' is a dependent scope" or no error at all.

# Options: 
-O2 -std=c++2a -Wall -Wextra

# Source Code:
template<typename T>
class A {
public:
    using type = T::type;
    /*A(T::type a) : mA{a} {}*/ // error: expected ')' before 'a'
    A(type a); // OK
    constexpr void a(T::type a) noexcept { // OK
        mA = a;
    }
    [[nodiscard]] constexpr T::type a() const noexcept { // OK
        return mA;
    }
private:
    T::type mA; // OK
};

template<typename T>
A<T>::A(T::type a) : mA{a} {} // OK


struct B {
    using type = int;
};

int main() {
    A<B> a{20};
    a.a(10);
    return a.a();
}
>From gcc-bugs-return-630286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:37:30 2019
Return-Path: <gcc-bugs-return-630286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84656 invoked by alias); 22 Jan 2019 14:37:29 -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 84369 invoked by uid 48); 22 Jan 2019 14:37:25 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88955] transparent_union for vector types not accepted
Date: Tue, 22 Jan 2019 14:37: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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:
Message-ID: <bug-88955-4-VQlwOFPV2c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88955-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: 2019-01/txt/msg03095.txt.bz2
Content-length: 594

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

--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Note, without the attribute gcc passes the union on an SSE register, so it
doesn't look like TImode on the union matters (otherwise it would be passed via
rdx:rax register pair):

typedef unsigned long u64x2 __attribute__ ((vector_size (16)));

typedef union
{
        u64x2   u64;
} v128;

v128 bar(v128 x);
v128 foo(v128 x)
{
    x.u64 *= -1;
    return bar(x);
}

foo:
        vpxor   %xmm1, %xmm1, %xmm1
        vpsubq  %xmm0, %xmm1, %xmm0
        jmp     bar
>From gcc-bugs-return-630287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:49:57 2019
Return-Path: <gcc-bugs-return-630287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5010 invoked by alias); 22 Jan 2019 14:49:56 -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 4906 invoked by uid 48); 22 Jan 2019 14:49:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83906] Random FAIL: libstdc++-prettyprinters/80276.cc whatis p4
Date: Tue, 22 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83906-4-gFMg8pjC5A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83906-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: 2019-01/txt/msg03096.txt.bz2
Content-length: 330

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

--- Comment #22 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Pedro, I'm seeing this again with GDB 8.2 (specifically gdb-8.2-6.fc29.x86_64).

Is it likely to be something different, or a GDB regression?

(I still want a libstdc++ fix that works for older GDB anyway).
>From gcc-bugs-return-630288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:51:08 2019
Return-Path: <gcc-bugs-return-630288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9707 invoked by alias); 22 Jan 2019 14:51:07 -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 9653 invoked by uid 48); 22 Jan 2019 14:51:02 -0000
From: "maratrus at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: maratrus at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88971-4-A30LQIkAxM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03097.txt.bz2
Content-length: 1736

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

--- Comment #7 from Marat Stanichenko <maratrus at mail dot ru> ---
(In reply to rguenther@suse.de from comment #6)
> > Do you believe that compiler can do better in such situations? Or the current
> > behaviour is perfectly valid and no improvements are really needed?
> 
> The compiler can of course do better when estimating the benefit of
> inlining.  It's just not entirely clear if it is reasonably easy to
> do so ... [let aside the -finline-function issue]

Is it only about inlining?

Unfortunately, I cannot evaluate the technical difficulties but in patterns
like presented here i.e.

```
if (condition)
  Function(param);
```

irrespective of the fact whether `Function()` is asked to be inlined or not
there are at least two observations that the compiler may notice before taking
an optimization decision:

a) Whether `Function(param)` is empty or not. In both scenarios in the example
presented `PrintBad<false>("<", ">", t)` and `PrintGood<false>("<", t)` are
actually empty.

b) Whether `param` is used in a `Function`. I think I can see the examples when
function calls like `PrintBad<false>(">", t)` generates a code to construct
parameter ">" despite the fact that not only it is not used but also the
function body is empty.

Of course, ideally I expect the parameter not to be constructed if it is not
used and the whole branch to be eliminated of the `Function` is empty and
`condition` does not have side effects. But as I said, I do not have enough
technical expertise to evaluate the cost. I speak from a solely user's
perspective.

What do you think is the best way to solve this? Keep tracking examples until
some critical mass is collected?
>From gcc-bugs-return-630289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 14:54:22 2019
Return-Path: <gcc-bugs-return-630289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22307 invoked by alias); 22 Jan 2019 14:54: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 22163 invoked by uid 55); 22 Jan 2019 14:54:16 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Tue, 22 Jan 2019 14:54: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88954-4-IGah2Fnkjc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg03098.txt.bz2
Content-length: 940

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

--- Comment #6 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Tue Jan 22 14:53:41 2019
New Revision: 268152

URL: https://gcc.gnu.org/viewcvs?rev=268152&root=gcc&view=rev
Log:
i386: Load external function address via GOT slot

With noplt attribute, we load the external function address via the GOT
slot so that linker won't create an PLT entry for extern function address.

gcc/

        PR target/88954
        * config/i386/i386.c (ix86_force_load_from_GOT_p): Also check
        noplt attribute.

gcc/testsuite/

        PR target/88954
        * gcc.target/i386/pr88954-1.c: New test.
        * gcc.target/i386/pr88954-2.c: Likewise.

Added:
    trunk/gcc/testsuite/gcc.target/i386/pr88954-1.c
    trunk/gcc/testsuite/gcc.target/i386/pr88954-2.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:03:29 2019
Return-Path: <gcc-bugs-return-630290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81763 invoked by alias); 22 Jan 2019 15:03:28 -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 81689 invoked by uid 48); 22 Jan 2019 15:03:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88968] [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88968-4-RfWdP3se3z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg03099.txt.bz2
Content-length: 578

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45495
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45495&action=edit
gcc9-pr88968.patch

Untested fix.
>From gcc-bugs-return-630291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:08:13 2019
Return-Path: <gcc-bugs-return-630291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105702 invoked by alias); 22 Jan 2019 15:08:12 -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 102737 invoked by uid 48); 22 Jan 2019 15:08:08 -0000
From: "tom at kera dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Tue, 22 Jan 2019 15:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tom at kera dot name
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:
Message-ID: <bug-88947-4-IP7T8tEz5o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg03100.txt.bz2
Content-length: 509

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

--- Comment #4 from Tomalak Geret'kal <tom at kera dot name> ---
To be honest I'd expect this in less trivial circumstances too. If, at a given
stage of processing, the only possible paths towards a match all require a
prefix that's already been ruled out, that should be an immediate return false.
To the best of my knowledge this is commonly what happens in regex engines
(though again libstdc++ is far from alone in the C++ world in not doing so!)
>From gcc-bugs-return-630292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:10:06 2019
Return-Path: <gcc-bugs-return-630292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8201 invoked by alias); 22 Jan 2019 15:10:05 -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 8115 invoked by uid 48); 22 Jan 2019 15:10:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83906] Random FAIL: libstdc++-prettyprinters/80276.cc whatis p4
Date: Tue, 22 Jan 2019 15:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83906-4-ZQOCTOgovZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83906-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: 2019-01/txt/msg03101.txt.bz2
Content-length: 389

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

--- Comment #23 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Actually, I wonder if it's caused by r264958 because 'std::string' is no longer
unambiguous in libstdc++.so

In some translation units it is a typedef for std::basic_string<char> and in
other translation units it is a typedef for std::__cxx11::basic_string<char>.
>From gcc-bugs-return-630293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:12:41 2019
Return-Path: <gcc-bugs-return-630293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14019 invoked by alias); 22 Jan 2019 15:12:41 -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 13960 invoked by uid 48); 22 Jan 2019 15:12:37 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Tue, 22 Jan 2019 15:12: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88877-4-uDIin0m25W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg03102.txt.bz2
Content-length: 1101

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

--- Comment #18 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Alan Modra from comment #17)
> > Is anything broken though?
> 
> Yes, as demonstrated by the testcase.

I couldn't get the testcase to link, I don't think I have an __floatunsidf
anywhere, so I cannot check.

> > If the libcall routines know they are called this way, all is fine.
> 
> They don't.  libgcc functions are mostly C code that can make use of the
> fact that on ppc64 an unsigned int arg will have the top 32 bits zeroed.

And since they are called without prototype, they should be defined without
prototype as well.  Why don't we do that?  Or is that no longer supported; in
that case, the definition should declare types as they will be passed manually.
Ugly and fragile.

> We avoid some potential problems with things like popcount by not having a
> popcountsi.  Instead we use popcountdi, and that results in gcc
> zero-extending a 32-bit value to 64 bits before we reach
> emit_library_call_value_1.

Wow, ugly.  And extra fragile :-(
>From gcc-bugs-return-630294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:18:17 2019
Return-Path: <gcc-bugs-return-630294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19666 invoked by alias); 22 Jan 2019 15:18:16 -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 19615 invoked by uid 48); 22 Jan 2019 15:18:13 -0000
From: "antony at cosmologist dot info" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88980] New: [9 regression] segfault on allocatable string member assignment
Date: Tue, 22 Jan 2019 15:18: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antony at cosmologist dot info
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88980-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: 2019-01/txt/msg03103.txt.bz2
Content-length: 1105

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

            Bug ID: 88980
           Summary: [9 regression] segfault on allocatable string member
                    assignment
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: antony at cosmologist dot info
  Target Milestone: ---

This code gives seg fault in 9.0.0 20181010 and 9.0.0 20190103, OK in 8.2.1:
(same with P pointer or allocatable)


    program tester
    call gbug
    contains

    subroutine gbug
    type TNameValue
        character(LEN=:), allocatable :: Name
    end type TNameValue

    type TNameValue_pointer
        Type(TNameValue), allocatable :: P
    end type TNameValue_pointer

    Type TType
        type(TNameValue_pointer), dimension(:), allocatable :: Items
    end type TType
    Type(TType) T

    allocate(T%Items(2))
    allocate(T%Items(2)%P)
    T%Items(2)%P%Name =  'test'

    end subroutine gbug

    end program tester
>From gcc-bugs-return-630295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:22:30 2019
Return-Path: <gcc-bugs-return-630295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25804 invoked by alias); 22 Jan 2019 15:22:29 -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 25714 invoked by uid 55); 22 Jan 2019 15:22:24 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88971] Branch optimization inconsistency (missed optimization)
Date: Tue, 22 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88971-4-lpUKmdBioK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88971-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: 2019-01/txt/msg03104.txt.bz2
Content-length: 2119

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

--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 22 Jan 2019, maratrus at mail dot ru wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88971
> 
> --- Comment #7 from Marat Stanichenko <maratrus at mail dot ru> ---
> (In reply to rguenther@suse.de from comment #6)
> > > Do you believe that compiler can do better in such situations? Or the current
> > > behaviour is perfectly valid and no improvements are really needed?
> > 
> > The compiler can of course do better when estimating the benefit of
> > inlining.  It's just not entirely clear if it is reasonably easy to
> > do so ... [let aside the -finline-function issue]
> 
> Is it only about inlining?
> 
> Unfortunately, I cannot evaluate the technical difficulties but in patterns
> like presented here i.e.
> 
> ```
> if (condition)
>   Function(param);
> ```
> 
> irrespective of the fact whether `Function()` is asked to be inlined or not
> there are at least two observations that the compiler may notice before taking
> an optimization decision:
> 
> a) Whether `Function(param)` is empty or not. In both scenarios in the example
> presented `PrintBad<false>("<", ">", t)` and `PrintGood<false>("<", t)` are
> actually empty.
> 
> b) Whether `param` is used in a `Function`. I think I can see the examples when
> function calls like `PrintBad<false>(">", t)` generates a code to construct
> parameter ">" despite the fact that not only it is not used but also the
> function body is empty.
> 
> Of course, ideally I expect the parameter not to be constructed if it is not
> used and the whole branch to be eliminated of the `Function` is empty and
> `condition` does not have side effects. But as I said, I do not have enough
> technical expertise to evaluate the cost. I speak from a solely user's
> perspective.
> 
> What do you think is the best way to solve this? Keep tracking examples until
> some critical mass is collected?

Well, it's more until any bright idea pops up how to solve this
abstraction issue...
>From gcc-bugs-return-630296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:24:53 2019
Return-Path: <gcc-bugs-return-630296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33684 invoked by alias); 22 Jan 2019 15:24:52 -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 33591 invoked by uid 48); 22 Jan 2019 15:24:46 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86756] Don't define __cpp_lib_filesystem unless --enable-libstdcxx-filesystem-ts
Date: Tue, 22 Jan 2019 15:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86756-4-CtVKjtWXOk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86756-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: 2019-01/txt/msg03105.txt.bz2
Content-length: 492

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

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
There are more changes needed to the library code, to stop using chdir, mkdir
etc. when not supported. This was first brought up in
https://gcc.gnu.org/ml/libstdc++/2019-01/msg00039.html 

I'm not sure how to detect whether those functions are usable though, because
apparently they're declared during compilation but absent when loading 
libstdc++.so at runtime.
>From gcc-bugs-return-630297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:40:10 2019
Return-Path: <gcc-bugs-return-630297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68435 invoked by alias); 22 Jan 2019 15:40:09 -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 68365 invoked by uid 48); 22 Jan 2019 15:40:04 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88981] New: [nvptx, openacc, libgomp] How to handle async regions without corresponding wait
Date: Tue, 22 Jan 2019 15:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88981-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: 2019-01/txt/msg03106.txt.bz2
Content-length: 2316

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

            Bug ID: 88981
           Summary: [nvptx, openacc, libgomp] How to handle async regions
                    without corresponding wait
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider this test-case:
...
/* { dg-do run } */

#include <stdlib.h>

int
main (void)
{
  int a[128];
  int N = 128;
#pragma acc parallel async
  {
    #pragma loop seq
    for (int i = 0; i < 1024 * 1024 * 10; ++i)
      a[i % N] += a[N - (i % N) - 1];
  }

  /* no #pragma acc wait */
  return 0;
}
...

Atm the moment, we run into PR88941:
...
async-no-wait.exe: libgomp/plugin/plugin-nvptx.c: map_fini: \
  Assertion `!s->map->active' failed.
...

Now, consider this patch:
...
diff --git a/libgomp/plugin/plugin-nvptx.c b/libgomp/plugin/plugin-nvptx.c
index dd2bcf3083f..e9b0e6c660a 100644
--- a/libgomp/plugin/plugin-nvptx.c
+++ b/libgomp/plugin/plugin-nvptx.c
@@ -489,6 +489,14 @@ fini_streams_for_device (struct ptx_device *ptx_dev)
       struct ptx_stream *s = ptx_dev->active_streams;
       ptx_dev->active_streams = ptx_dev->active_streams->next;

+      {
+       CUresult r;
+       r = CUDA_CALL_NOCHECK (cuStreamQuery, s->stream);
+       if (r == CUDA_ERROR_NOT_READY)
+         GOMP_PLUGIN_error ("Stream destroyed with operation incomplete."
+                            " Forgot to wait on async?");
+      }
+
       ret &= map_fini (s);

       CUresult r = CUDA_CALL_NOCHECK (cuStreamDestroy, s->stream);
...

which gets us:
...
libgomp: Stream destroyed with operation incomplete. Forgot to wait on async?
async-no-wait.exe: libgomp/plugin/plugin-nvptx.c: map_fini: \
  Assertion `!s->map->active' failed.
...

So, the question is, how to handle async launches without corresponding wait?

It might be good to notify the user about it, as above patch does (though
perhaps not notify using GOMP_PLUGIN_error, but GOMP_PLUGIN_warning or some
such).

In the case that we call acc_shutdown, it's considered an error if a stream is
still running, so we could not just notify, but error out.
>From gcc-bugs-return-630298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 15:43:39 2019
Return-Path: <gcc-bugs-return-630298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85906 invoked by alias); 22 Jan 2019 15:43:37 -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 85855 invoked by uid 48); 22 Jan 2019 15:43:32 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88981] [nvptx, openacc, libgomp] How to handle async regions without corresponding wait
Date: Tue, 22 Jan 2019 15:43: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords cf_gcctarget cc
Message-ID: <bug-88981-4-GdkPBtP4Zy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88981-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: 2019-01/txt/msg03107.txt.bz2
Content-length: 736

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |openacc
             Target|                            |nvptx
                 CC|                            |cltang at gcc dot gnu.org,
                   |                            |tschwinge at gcc dot gnu.org

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Chung-Lin, 

how would this test-case be handled using the async patch set for gcc 10 stage
1? Is there something done in the generic openacc code?

Thanks,
- Tom
>From gcc-bugs-return-630299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:08:56 2019
Return-Path: <gcc-bugs-return-630299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105740 invoked by alias); 22 Jan 2019 16:08:55 -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 105672 invoked by uid 55); 22 Jan 2019 16:08:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88740] [7/8/9 Regression] libstdc++ tests no longer print assertion failure messages
Date: Tue, 22 Jan 2019 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88740-4-8qivrxg5ai@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88740-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: 2019-01/txt/msg03108.txt.bz2
Content-length: 567

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jan 22 16:08:18 2019
New Revision: 268154

URL: https://gcc.gnu.org/viewcvs?rev=268154&root=gcc&view=rev
Log:
PR libstdc++/88740 Print assertion messages to stderr

        PR libstdc++/88740
        * testsuite/util/testsuite_hooks.h [stderr] (VERIFY): Use fprintf to
        write to stderr instead of using printf.

Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/testsuite/util/testsuite_hooks.h
>From gcc-bugs-return-630300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:09:19 2019
Return-Path: <gcc-bugs-return-630300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106704 invoked by alias); 22 Jan 2019 16:09:17 -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 106598 invoked by uid 48); 22 Jan 2019 16:09:13 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88740] [7/8 Regression] libstdc++ tests no longer print assertion failure messages
Date: Tue, 22 Jan 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: bug_status cf_reconfirmed_on short_desc everconfirmed
Message-ID: <bug-88740-4-jCJFXx9lla@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88740-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: 2019-01/txt/msg03109.txt.bz2
Content-length: 765

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
            Summary|[7/8/9 Regression]          |[7/8 Regression] libstdc++
                   |libstdc++ tests no longer   |tests no longer print
                   |print assertion failure     |assertion failure messages
                   |messages                    |
     Ever confirmed|0                           |1

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk so far.
>From gcc-bugs-return-630301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:11:11 2019
Return-Path: <gcc-bugs-return-630301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108912 invoked by alias); 22 Jan 2019 16:11: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 108842 invoked by uid 48); 22 Jan 2019 16:11:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Tue, 22 Jan 2019 16:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88933-4-C3w2RPwcGA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03110.txt.bz2
Content-length: 551

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
gimple_merge_blocks is called in between, which merges a bb with that
1073741825 with one with 445388109 count and nothing updates the call edge
count after that adjustment.
>From gcc-bugs-return-630302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:17:07 2019
Return-Path: <gcc-bugs-return-630302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72045 invoked by alias); 22 Jan 2019 16:17:06 -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 62457 invoked by uid 48); 22 Jan 2019 16:17:00 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Tue, 22 Jan 2019 16:17: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-AuUFJG0QZ7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg03111.txt.bz2
Content-length: 462

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

--- Comment #20 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Oh, sorry, I missed that in all the commentary.  I had looked at the code and
seen the "obvious" problem in the expansion, and noted you had suggested that
also.  Should have read further.

I think that's right, using this is wrong for LE.  Jakub, do you want to push
that patch, or shall I regstrap it once more and take care of it?
>From gcc-bugs-return-630303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:19:41 2019
Return-Path: <gcc-bugs-return-630303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26766 invoked by alias); 22 Jan 2019 16:19:39 -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 26633 invoked by uid 48); 22 Jan 2019 16:19:34 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Tue, 22 Jan 2019 16:19: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-3bxPGJV3cP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg03112.txt.bz2
Content-length: 237

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

--- Comment #21 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
We should probably disable the _v4sf_scalar one for LE also, as this seems to
be doing a similar trick for V4SF.
>From gcc-bugs-return-630304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:20:38 2019
Return-Path: <gcc-bugs-return-630304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28664 invoked by alias); 22 Jan 2019 16:20:37 -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 28586 invoked by uid 48); 22 Jan 2019 16:20:33 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Tue, 22 Jan 2019 16:20: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-VjFTxdfA4t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg03113.txt.bz2
Content-length: 180

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

--- Comment #22 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
(I'll test with both disabled for LE and report results.)
>From gcc-bugs-return-630305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:21:03 2019
Return-Path: <gcc-bugs-return-630305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29528 invoked by alias); 22 Jan 2019 16:21:02 -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 29468 invoked by uid 55); 22 Jan 2019 16:20:58 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88909] struct builtin_description doesn't support ix86_isa_flags2
Date: Tue, 22 Jan 2019 16:21: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88909-4-nAPX0oB3OL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88909-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88909-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: 2019-01/txt/msg03114.txt.bz2
Content-length: 1802

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

--- Comment #1 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Tue Jan 22 16:20:25 2019
New Revision: 268155

URL: https://gcc.gnu.org/viewcvs?rev=268155&root=gcc&view=rev
Log:
i386: Add mask2 to builtin_description

There are

struct builtin_description
{
  const HOST_WIDE_INT mask;
  const enum insn_code icode;
  const char *const name;
  const enum ix86_builtins code;
  const enum rtx_code comparison;
  const int flag;
};

Since "mask" is used for both ix86_isa_flags and ix86_isa_flags2, buitins
with both flags can't be handled easily.  This patch adds mask2 to
builtin_description to handle it properly.

2019-01-22  Hongtao Liu  <hongtao.liu@intel.com>
            H.J. Lu  <hongjiu.lu@intel.com>

        PR target/88909
        * config/i386/i386-builtin.def: Add mask2 to all builtin
        initializations.  Merge ARGS2 and SPECIAL_ARGS2 into ARGS and
        SPECIAL_ARGS.
        * config/i386/i386.c (BDESC): Add mask2 to the definition.
        (BDESC_FIRST): Likewise.
        (define_builtin): Add an argument for mask2.  Updated to handle
        both ix86_isa_flags and ix86_isa_flags2.
        (define_builtin_const): Likewise.
        (define_builtin_pure): Likewise.
        (define_builtin2): Deleted.
        (define_builtin_const2): Likewise.
        (builtin_description): Add a member, mask2.
        (bdesc_*): Add mask2 to builtin initializations.
        (ix86_init_mmx_sse_builtins): Update calls to def_builtin,
        def_builtin_const and def_builtin_pure.  Remove SPECIAL_ARGS2
        support.
        (ix86_get_builtin_func_type): Remove SPECIAL_ARGS2 support.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386-builtin.def
    trunk/gcc/config/i386/i386.c
>From gcc-bugs-return-630308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:26:44 2019
Return-Path: <gcc-bugs-return-630308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35600 invoked by alias); 22 Jan 2019 16:26:44 -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 35526 invoked by uid 48); 22 Jan 2019 16:26:39 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88983] New: ICE in label_matches, at cp/constexpr.c:4035
Date: Tue, 22 Jan 2019 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88983-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: 2019-01/txt/msg03117.txt.bz2
Content-length: 4421

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

            Bug ID: 88983
           Summary: ICE in label_matches, at cp/constexpr.c:4035
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107), 8.2, 7.4, 6.3 ICE when compiling
the following testcase reduced from test/SemaCXX/constant-expression-cxx1y.cpp
from the clang 7.0.1 testsuite:

constexpr int
ni (int ay)
{
  switch (ay)
    {
      if (1)
        {
          case 1:
            return 1;
        }
      else
        {
          default:
            ;
        }
    }

  return 0;
}

static_assert (ni (1), "");

% g++-9.0.0-alpha20190120 -c xd96vus4.cpp
xd96vus4.cpp:21:19:   in 'constexpr' expansion of 'ni(1)'
xd96vus4.cpp:21:27: internal compiler error: in label_matches, at
cp/constexpr.c:4035
   21 | static_assert (ni (1), "");
      |                           ^
0x5cde7e label_matches
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4035
0x8cc336 cxx_eval_constant_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4223
0x8cc53c cxx_eval_constant_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4484
0x8ccd7f cxx_eval_switch_expr
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4148
0x8ccd7f cxx_eval_constant_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4938
0x8cce62 cxx_eval_statement_list
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4073
0x8cce62 cxx_eval_constant_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4836
0x8cba23 cxx_eval_call_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:1799
0x8cc800 cxx_eval_constant_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4357
0x8d2672 cxx_eval_outermost_constant_expr
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:5095
0x8d2dc8 maybe_constant_value(tree_node*, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:5327
0x8e5265 cp_fully_fold(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:2163
0xa63fa4 cp_build_binary_op(op_location_t const&, tree_code, tree_node*,
tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/typeck.c:5538
0xa66aac build_binary_op(unsigned int, tree_code, tree_node*, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/typeck.c:4246
0xa66b2b cp_truthvalue_conversion(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/typeck.c:5864
0x8e9d8d ocp_convert(tree_node*, tree_node*, int, int, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cvt.c:844
0x8eb37d cp_convert(tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cvt.c:637
0x8eb37d cp_convert_and_check(tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cvt.c:656
0x896934 convert_like_real
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/call.c:7327
0x897af0 perform_implicit_conversion_flags(tree_node*, tree_node*, int, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/call.c:11043
>From gcc-bugs-return-630307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:26:34 2019
Return-Path: <gcc-bugs-return-630307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34850 invoked by alias); 22 Jan 2019 16:26:33 -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 34801 invoked by uid 48); 22 Jan 2019 16:26:29 -0000
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Tue, 22 Jan 2019 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: timshen 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:
Message-ID: <bug-88947-4-wQ11nhKKzl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg03116.txt.bz2
Content-length: 737

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

--- Comment #5 from Tim Shen <timshen at gcc dot gnu.org> ---
(In reply to Tomalak Geret'kal from comment #4)
> To be honest I'd expect this in less trivial circumstances too. If, at a
> given stage of processing, the only possible paths towards a match all
> require a prefix that's already been ruled out, that should be an immediate
> return false. To the best of my knowledge this is commonly what happens in
> regex engines (though again libstdc++ is far from alone in the C++ world in
> not doing so!)

For the original test case, have you tried regex_match() with "what.*"?

Do you have any non-trivial testcase in mind that is still unexpectedly slow
with regex_match()?
>From gcc-bugs-return-630306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:26:22 2019
Return-Path: <gcc-bugs-return-630306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34135 invoked by alias); 22 Jan 2019 16:26: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 34113 invoked by uid 48); 22 Jan 2019 16:26:17 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88982] New: ICE in tsubst_pack_expansion, at cp/pt.c:12221
Date: Tue, 22 Jan 2019 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88982-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: 2019-01/txt/msg03115.txt.bz2
Content-length: 3928

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

            Bug ID: 88982
           Summary: ICE in tsubst_pack_expansion, at cp/pt.c:12221
           Product: gcc
           Version: 8.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICE when compiling the following
testcase reduced from test/CXX/temp/temp.param/p15-cxx0x.cpp from the clang
7.0.1 testsuite:

template<typename...Ts> struct A {
  template<template<typename, Ts = 0> class ...Cs, Cs<Ts> ...Vs> struct B {
    B() {
    }
  };
};

template<typename, int> using Int = int;
template<typename, short> using Char = char;
A<int, short>::B<Int, Char> b;

% g++-9.0.0-alpha20190120 -c rtzrooh4.cpp
rtzrooh4.cpp:10:27: internal compiler error: in tsubst_pack_expansion, at
cp/pt.c:12221
   10 | A<int, short>::B<Int, Char> b;
      |                           ^
0x63d616 tsubst_pack_expansion(tree_node*, tree_node*, int, tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:12221
0x9ef5bb coerce_template_parameter_pack
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:8121
0x9ef5bb coerce_template_parms
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:8411
0x9f08a1 coerce_innermost_template_parms
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:8619
0x9fcaaa lookup_template_class_1
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:9324
0x9fcaaa lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*,
int, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:9683
0xa29c8b finish_template_type(tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/semantics.c:3255
0x9a4aad cp_parser_template_id
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:16406
0x9a4c66 cp_parser_class_name
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:23127
0x9a8b42 cp_parser_qualifying_entity
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:6683
0x9a8b42 cp_parser_nested_name_specifier_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:6369
0x99c9ab cp_parser_constructor_declarator_p
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27312
0x99c9ab cp_parser_decl_specifier_seq
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:14038
0x99d2a4 cp_parser_simple_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13354
0x9c2c10 cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13173
0x9c33a0 cp_parser_translation_unit
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:4698
0x9c33a0 c_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:41003
0xaccdab c_common_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-opts.c:1155
>From gcc-bugs-return-630310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:27:23 2019
Return-Path: <gcc-bugs-return-630310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37447 invoked by alias); 22 Jan 2019 16:27: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 37279 invoked by uid 48); 22 Jan 2019 16:27:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Tue, 22 Jan 2019 16:27: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-87064-4-UQh009O40B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg03119.txt.bz2
Content-length: 758

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

--- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45496
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45496&action=edit
gcc9-pr87064.patch

Patch I've so far tested on powerpc64le-linux only, where it fixed
FAIL: libgomp.oacc-fortran/reduction-3.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1  -O1  execution test
and didn't regress anything else.  I can bootstrap/regtest even on
powerpc64-linux (though I believe it is pointless, given that I know from the
earlier statistics gathering that the pattern is never used on powerpc64-linux
during bootstrap nor -m32/-m64 regtest).
So, I'll post to gcc-patches.  The v4sf_scalar I'll leave to you, ok?
>From gcc-bugs-return-630309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:27:04 2019
Return-Path: <gcc-bugs-return-630309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36473 invoked by alias); 22 Jan 2019 16:27: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 36403 invoked by uid 48); 22 Jan 2019 16:27:00 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88984] New: [9 Regression] ICE in genericize_switch_stmt, at cp/cp-gimplify.c:377
Date: Tue, 22 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88984-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: 2019-01/txt/msg03118.txt.bz2
Content-length: 4214

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

            Bug ID: 88984
           Summary: [9 Regression] ICE in genericize_switch_stmt, at
                    cp/cp-gimplify.c:377
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
testcase extracted from test/Sema/loop-control.c from the clang 7.0.1
testsuite:

void pr8880_18(int x, int y) {
  while(x > 0)
    switch(({if(y) break; y;})) {
    case 2: x = 0;
    }
}

% g++-9.0.0-alpha20190120 -c rqxhnkhh.c
rqxhnkhh.c: In function 'void pr8880_18(int, int)':
rqxhnkhh.c:6:1: internal compiler error: in genericize_switch_stmt, at
cp/cp-gimplify.c:377
    6 | }
      | ^
0x5d9807 genericize_switch_stmt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:377
0x5d9807 cp_genericize_r
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:1505
0x1273013 walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, default_hash_traits<tree_node*> >*, tree_node*
(*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*), void*,
hash_set<tree_node*, default_hash_traits<tree_node*> >*))
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.c:12064
0x8dc138 genericize_cp_loop
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:251
0x8df2ca genericize_do_stmt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:346
0x8df2ca cp_genericize_r
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:1501
0x1273013 walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, default_hash_traits<tree_node*> >*, tree_node*
(*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*), void*,
hash_set<tree_node*, default_hash_traits<tree_node*> >*))
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.c:12064
0x8e0bd2 cp_genericize_tree
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:1629
0x8e0f94 cp_genericize(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/cp-gimplify.c:1778
0x91a65d finish_function(bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl.c:16183
0x9bb2f8 cp_parser_function_definition_after_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27633
0x9bc0dc cp_parser_function_definition_from_specifiers_and_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27546
0x9bc0dc cp_parser_init_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:20205
0x99d398 cp_parser_simple_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13476
0x9c2c10 cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13173
0x9c33a0 cp_parser_translation_unit
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:4698
0x9c33a0 c_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:41003
0xaccdab c_common_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-opts.c:1155
>From gcc-bugs-return-630311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:33:25 2019
Return-Path: <gcc-bugs-return-630311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98065 invoked by alias); 22 Jan 2019 16:33:24 -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 97980 invoked by uid 55); 22 Jan 2019 16:33:19 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] ICE in extract_insn, at recog.c:2304
Date: Tue, 22 Jan 2019 16:33: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uros at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88938-4-prg9nlOOK8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88938-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: 2019-01/txt/msg03120.txt.bz2
Content-length: 721

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

--- Comment #4 from uros at gcc dot gnu.org ---
Author: uros
Date: Tue Jan 22 16:32:47 2019
New Revision: 268156

URL: https://gcc.gnu.org/viewcvs?rev=268156&root=gcc&view=rev
Log:
        PR target/88938
        * config/i386/i386.c (ix86_expand_builtin) [case IX86_BUILTIN_BEXTRI32,
        case IX86_BUILTIN_BEXTRI64]: Sanitize operands.

testsuite/ChangeLog:

        PR target/88938
        * gcc.target/i386/pr88938.c: New test.


Added:
    branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/pr88938.c
Modified:
    branches/gcc-8-branch/gcc/ChangeLog
    branches/gcc-8-branch/gcc/config/i386/i386.c
    branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:35:52 2019
Return-Path: <gcc-bugs-return-630312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100873 invoked by alias); 22 Jan 2019 16:35:52 -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 100796 invoked by uid 48); 22 Jan 2019 16:35:47 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 16:35: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88965-4-Ev9oXD4B5A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg03121.txt.bz2
Content-length: 178

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

--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
That patch looks good, and is pre-approved.  Thanks!
>From gcc-bugs-return-630313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:36:30 2019
Return-Path: <gcc-bugs-return-630313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103112 invoked by alias); 22 Jan 2019 16:36:29 -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 103055 invoked by uid 55); 22 Jan 2019 16:36:26 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] ICE in extract_insn, at recog.c:2304
Date: Tue, 22 Jan 2019 16:36: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uros at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88938-4-GNu7W1BI3c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88938-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: 2019-01/txt/msg03122.txt.bz2
Content-length: 721

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

--- Comment #5 from uros at gcc dot gnu.org ---
Author: uros
Date: Tue Jan 22 16:35:53 2019
New Revision: 268157

URL: https://gcc.gnu.org/viewcvs?rev=268157&root=gcc&view=rev
Log:
        PR target/88938
        * config/i386/i386.c (ix86_expand_builtin) [case IX86_BUILTIN_BEXTRI32,
        case IX86_BUILTIN_BEXTRI64]: Sanitize operands.

testsuite/ChangeLog:

        PR target/88938
        * gcc.target/i386/pr88938.c: New test.


Added:
    branches/gcc-7-branch/gcc/testsuite/gcc.target/i386/pr88938.c
Modified:
    branches/gcc-7-branch/gcc/ChangeLog
    branches/gcc-7-branch/gcc/config/i386/i386.c
    branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:47:48 2019
Return-Path: <gcc-bugs-return-630314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66511 invoked by alias); 22 Jan 2019 16:47:45 -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 62171 invoked by uid 48); 22 Jan 2019 16:47:40 -0000
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Tue, 22 Jan 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: timshen 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:
Message-ID: <bug-88947-4-mT6unERgNZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg03123.txt.bz2
Content-length: 1451

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

--- Comment #6 from Tim Shen <timshen at gcc dot gnu.org> ---
(In reply to Tomalak Geret'kal from comment #4)
> To be honest I'd expect this in less trivial circumstances too. If, at a
> given stage of processing, the only possible paths towards a match all
> require a prefix that's already been ruled out, that should be an immediate
> return false.

Thinking about this more, I think it's also easy to support the following case:
regex_search(..., regex("{arbitrary_literal_string}...")
where {arbitrary_literal_string} is a literal string, without other regex magic
like "|" or "*". The literal prefix should be passed into a substring search.

For implemention:
The new algorithm for regex_search() would be:
(1) prefix = find the longest deterministic prefix of the regex
(2) pos = find the first occurance of the prefix in the target. If it fails,
return false.
(3) target = target[pos+prefix.size():]
(4) try match target from start (as it's currently done)
(5) if (4) fails, go to (2).

(1) can be done at regex-compiling time. It'd require a new data member thus
non-ABI compatible. (1) can also be done at matching time. Either way, we are
looking for the longest sequence of literals from start. It stops with any of
"*", "?", "(" or any other magic.

(2) can be as plain as a substring search, but one might prefer the O(n) KMP
algorithm if we happen to have one.
>From gcc-bugs-return-630316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:49:24 2019
Return-Path: <gcc-bugs-return-630316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86071 invoked by alias); 22 Jan 2019 16:49:24 -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 85667 invoked by uid 48); 22 Jan 2019 16:49:20 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88938] ICE in extract_insn, at recog.c:2304
Date: Tue, 22 Jan 2019 16: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88938-4-PM4sgByZtl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88938-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: 2019-01/txt/msg03125.txt.bz2
Content-length: 429

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Fixed.
>From gcc-bugs-return-630315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:49:21 2019
Return-Path: <gcc-bugs-return-630315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85686 invoked by alias); 22 Jan 2019 16:49: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 85558 invoked by uid 48); 22 Jan 2019 16:49:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88984] [9 Regression] ICE in genericize_switch_stmt, at cp/cp-gimplify.c:377
Date: Tue, 22 Jan 2019 16:49: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed
Message-ID: <bug-88984-4-fbg6T2PhAY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88984-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: 2019-01/txt/msg03124.txt.bz2
Content-length: 738

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-22
                 CC|                            |jakub at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with my r255218 (C++ only), let me have a look.
>From gcc-bugs-return-630317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:55:49 2019
Return-Path: <gcc-bugs-return-630317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37572 invoked by alias); 22 Jan 2019 16:55:49 -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 27528 invoked by uid 48); 22 Jan 2019 16:55:42 -0000
From: "tom at kera dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88947] regex_match doesn't fail early when given a non-matching pattern with a start-of-input anchor
Date: Tue, 22 Jan 2019 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tom at kera dot name
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:
Message-ID: <bug-88947-4-BkO9Ba8BBU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88947-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: 2019-01/txt/msg03126.txt.bz2
Content-length: 1203

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

--- Comment #7 from Tomalak Geret'kal <tom at kera dot name> ---
(In reply to Tim Shen from comment #5)
> For the original test case, have you tried regex_match() with "what.*"?

That behaves as I'd expect
(http://quick-bench.com/AKdMnnhA03T1vwfN9sf53xlbD6s).

> Do you have any non-trivial testcase in mind that is still unexpectedly slow
> with regex_match()?

The original real-world pattern that led to me discovering this was:

/^[\x02-\x7f]\0..[\x01-\x0c]\0..\0\0/

Switching to regex_match() for that pattern also yields the expected result
(http://quick-bench.com/g6lZj00gBswzvd-rjO7QwRE0Exg), so that's a good
workaround here.

But, adapting your earlier example to "(^abc|xyz)", this would require chaining
a regex_match with a regex_search, which gets unwieldy quite quickly.

Well, okay, I suppose in that example we could regex_match on
"(?:(abc).*|.*(xyz).*)", but I really don't think we should have to rewrite
patterns like this in order to get the behaviour that's common in other
ecosystems' regex impls. So, although I'm open to being convinced otherwise, I
still think we would reasonably expect regex_search to fail fast.
>From gcc-bugs-return-630318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:57:59 2019
Return-Path: <gcc-bugs-return-630318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17968 invoked by alias); 22 Jan 2019 16:57:58 -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 15755 invoked by uid 48); 22 Jan 2019 16:57:54 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 16:57: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail 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-88967-4-mbvAEQkm5N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg03127.txt.bz2
Content-length: 593

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

--- Comment #5 from Roman Lebedev <lebedev.ri at gmail dot com> ---
(In reply to Jakub Jelinek from comment #1)
> I've asked the ifort/clang maintainers about why they keep violating the
> standard, but haven't heard back from them.  And I must say I was trying
> hard to readd the above rule + exception, but haven't succeeded.
Uhm, apparently clang does implement it correctly:
https://godbolt.org/z/_HFUki
the default OpenMP version used is still 3.1, thus it is not noticeable.

This begs the question, does gcc have a similar switch?
>From gcc-bugs-return-630319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:58:14 2019
Return-Path: <gcc-bugs-return-630319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21311 invoked by alias); 22 Jan 2019 16:58:14 -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 21201 invoked by uid 48); 22 Jan 2019 16:58:10 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88973] [8/9 Regression] New -Wrestrict warning since r268048
Date: Tue, 22 Jan 2019 16:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: blocked
Message-ID: <bug-88973-4-9In1z98Y7U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88973-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: 2019-01/txt/msg03128.txt.bz2
Content-length: 2035

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |84774

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
I feel like I have seen this translation unit before.  The warning is by
design: for calls to strcpy with the same destination and source arrays, where
the algorithm cannot prove that an overlap doesn't occur it issues a "may
overlap" kind of a warning.  The offset ranges make it clear (to me at least)
that the warning algorithm thinks the overlap is possible but not inevitable. 
For example, this triggers it:

  void f (char *p, int i)
  {
    if (i < 0)
      i = 0;

    char *q = p + i;

    __builtin_strcpy (q, p);
  }

  t.c:10:3: warning: â€˜__builtin_strcpyâ€™ accessing 1 byte at offsets [0,
2147483647] and 0 may overlap 1 byte at offset 0 [-Wrestrict]
     10 |   __builtin_strcpy (q, p);
        |   ^~~~~~~~~~~~~~~~~~~~~~~

The logic behind the decision is that since using strcpy to copy within the
same array is only safe when one knows the length of the source string (in
addition to the distance between the offsets into the array), using a "bounded"
function such as memcpy or even strncpy would be more appropriate: it would
make the constraints explicit without sacrificing efficiency or readability.

GCC 8 doesn't issue the warning here because the bug fixed in r268048 on the
trunk but not yet backported to gcc-8-branch gets in the way: the offset in the
POINTER_PLUS_EXPR is in the anti-range ~[INT_MAX + 1, INT_MIN] which GCC 8
doesn't handle correctly.  I haven't backported r268048 to GCC 8 yet but I
don't think this warning is a reason not to.  Richard, let me know if you feel
otherwise.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84774
[Bug 84774] [meta-bug] bogus/missing -Wrestrict
>From gcc-bugs-return-630320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:58:17 2019
Return-Path: <gcc-bugs-return-630320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21570 invoked by alias); 22 Jan 2019 16:58:16 -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 21247 invoked by uid 48); 22 Jan 2019 16:58:12 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88909] struct builtin_description doesn't support ix86_isa_flags2
Date: Tue, 22 Jan 2019 16:58: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-88909-4-pXdddPUk50@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88909-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88909-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: 2019-01/txt/msg03129.txt.bz2
Content-length: 478

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |9.0

--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 9.
>From gcc-bugs-return-630321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 16:59:58 2019
Return-Path: <gcc-bugs-return-630321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24009 invoked by alias); 22 Jan 2019 16:59:56 -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 23929 invoked by uid 48); 22 Jan 2019 16:59:53 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88973] [8/9 Regression] New -Wrestrict warning since r268048
Date: Tue, 22 Jan 2019 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88973-4-q10G2l8mVt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88973-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: 2019-01/txt/msg03130.txt.bz2
Content-length: 411

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

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Created attachment 45497
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45497&action=edit
canonicalize_pathname function extracted from the translation unit.

Attached is the canonicalize_pathname function extracted from the translation
unit that triggers the -Wrestrict warning.
>From gcc-bugs-return-630322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:01:09 2019
Return-Path: <gcc-bugs-return-630322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25520 invoked by alias); 22 Jan 2019 17:00:42 -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 24910 invoked by uid 48); 22 Jan 2019 17:00:06 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88979] [C++20] P0634R3 not working for constructor parameter types
Date: Tue, 22 Jan 2019 17: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-88979-4-hEkTkeRq66@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88979-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88979-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: 2019-01/txt/msg03131.txt.bz2
Content-length: 764

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-22
                 CC|                            |mpolacek at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |mpolacek at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I'll look though I'm not sure yet if there's an actual bug.  Is there a version
with 'typename's included that compiles?
>From gcc-bugs-return-630323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:03:27 2019
Return-Path: <gcc-bugs-return-630323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46348 invoked by alias); 22 Jan 2019 17:03:26 -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 43742 invoked by uid 48); 22 Jan 2019 17:03:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 17:03: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
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-88967-4-GzhCtd4cnW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg03132.txt.bz2
Content-length: 269

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
No, gcc always implements just one OpenMP version, the latest one that has
support written.
Defaulting to almost 8 years old OpenMP version is weird.
>From gcc-bugs-return-630324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:06:42 2019
Return-Path: <gcc-bugs-return-630324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26384 invoked by alias); 22 Jan 2019 17:06:41 -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 24269 invoked by uid 48); 22 Jan 2019 17:06:37 -0000
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Tue, 22 Jan 2019 17:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sje at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-Vuf7E3rJmo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03133.txt.bz2
Content-length: 1744

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

--- Comment #21 from Steve Ellcey <sje at gcc dot gnu.org> ---
If I look at this specific example:

int f2 (int x, int y)
{
  return (x & ~0x0ff000) | ((y & 0x0ff) << 12);
}


Before the combine change, I see in x.c.260r.combine:

Trying 8, 9 -> 15:
    8: r98:SI=x1:SI<<0xc&0xff000
      REG_DEAD x1:SI
    9: r99:SI=x0:SI&0xfffffffffff00fff
      REG_DEAD x0:SI
   15: x0:SI=r98:SI|r99:SI
      REG_DEAD r98:SI
      REG_DEAD r99:SI
Successfully matched this instruction:
(set (zero_extract:SI (reg/i:SI 0 x0)
        (const_int 8 [0x8])
        (const_int 12 [0xc]))
    (zero_extend:SI (reg:QI 1 x1 [ y ])))
allowing combination of insns 8, 9 and 15
original costs 4 + 4 + 4 = 12
replacement cost 4
deferring deletion of insn with uid = 9.


Immediately after the combine change, I get:

Trying 8, 9 -> 15:
    8: r98:SI=r101:SI<<0xc&0xff000
      REG_DEAD r101:SI
    9: r99:SI=r100:SI&0xfffffffffff00fff
      REG_DEAD r100:SI
   15: x0:SI=r98:SI|r99:SI
      REG_DEAD r98:SI
      REG_DEAD r99:SI
Failed to match this instruction:
(set (reg/i:SI 0 x0)
    (ior:SI (and:SI (reg:SI 100)
            (const_int -1044481 [0xfffffffffff00fff]))
        (and:SI (ashift:SI (reg:SI 101)
                (const_int 12 [0xc]))
            (const_int 1044480 [0xff000]))))
Successfully matched this instruction:
(set (reg:SI 99)
    (ashift:SI (reg:SI 101)
        (const_int 12 [0xc])))
Failed to match this instruction:
(set (reg/i:SI 0 x0)
    (ior:SI (and:SI (reg:SI 100)
            (const_int -1044481 [0xfffffffffff00fff]))
        (and:SI (reg:SI 99)
            (const_int 1044480 [0xff000]))))


Is this because of x0 (a hard register) at the destination in insn 15?
>From gcc-bugs-return-630325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:07:15 2019
Return-Path: <gcc-bugs-return-630325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38930 invoked by alias); 22 Jan 2019 17:07:15 -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 38879 invoked by uid 48); 22 Jan 2019 17:07:11 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/88911] No "did you mean" for incorrect -dumpspecs option
Date: Tue, 22 Jan 2019 17:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88911-4-lWuxNZOpLu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88911-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88911-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: 2019-01/txt/msg03134.txt.bz2
Content-length: 196

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

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01311.html
>From gcc-bugs-return-630326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:09:52 2019
Return-Path: <gcc-bugs-return-630326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51384 invoked by alias); 22 Jan 2019 17:09:51 -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 51271 invoked by uid 48); 22 Jan 2019 17:09:47 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88294] [9 Regression] ICE on (invalid) C++11 code: in tsubst_copy, at cp/pt.c:15391
Date: Tue, 22 Jan 2019 17:09: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88294-4-VTokw2Je5z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88294-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: 2019-01/txt/msg03135.txt.bz2
Content-length: 187

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

--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I can try.  Unfortunately, the patch for 86476 doesn't fix this.
>From gcc-bugs-return-630327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:10:10 2019
Return-Path: <gcc-bugs-return-630327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52955 invoked by alias); 22 Jan 2019 17:10:09 -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 52797 invoked by uid 48); 22 Jan 2019 17:10:05 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 17:10: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail 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-88967-4-yZXA4aHSeW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg03136.txt.bz2
Content-length: 578

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

--- Comment #7 from Roman Lebedev <lebedev.ri at gmail dot com> ---
(In reply to Jakub Jelinek from comment #6)
> No, gcc always implements just one OpenMP version, the latest one that has
> support written.
E.g. because of this everyone affected will need to either just completely drop
"default(none)", or litter the code with "OMP4SHARED(<vars>)" which will expand
to nothing for older gcc, and to "shared(<vars>)" for gcc9.

That does look 'weird' too :)

> Defaulting to almost 8 years old OpenMP version is weird.
>From gcc-bugs-return-630328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:16:32 2019
Return-Path: <gcc-bugs-return-630328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68651 invoked by alias); 22 Jan 2019 17:16:32 -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 68444 invoked by uid 48); 22 Jan 2019 17:16:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 17:16: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
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-88967-4-T1Wcko5av7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg03137.txt.bz2
Content-length: 459

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, in your case firstprivate is really what you want, unless the compiler
figures that out for you magically you want to firstprivatize these variables. 
A different thing is of course if you have a large const aggregate, then it
might not be always a win.  But for an integral/pointer variable or similar, it
is definitely a win.
>From gcc-bugs-return-630331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:22:38 2019
Return-Path: <gcc-bugs-return-630331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103298 invoked by alias); 22 Jan 2019 17:22:37 -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 96180 invoked by uid 48); 22 Jan 2019 17:22:34 -0000
From: "lebedev.ri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 17:22: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lebedev.ri at gmail 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-88967-4-h0EvVI3SAO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg03140.txt.bz2
Content-length: 839

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

--- Comment #9 from Roman Lebedev <lebedev.ri at gmail dot com> ---
(In reply to Jakub Jelinek from comment #8)
> Well, in your case firstprivate is really what you want, unless the compiler
> figures that out for you magically you want to firstprivatize these
> variables.

Hm, i understand that this is going further off-topic, but can you
explain/point to some reading material as to why firstprivate() is the thing i
want,
instead of shared()? The variables are already const, i won't be modifying them
in any case. How is it better to make a copy of them for each thread, instead
of using the same single variable?

Perhaps that was the motivational reason for that OpenMP spec change,
and i'm missing something very subtle yet important?

Anyway, thank you for replying.
>From gcc-bugs-return-630329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:22:09 2019
Return-Path: <gcc-bugs-return-630329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62165 invoked by alias); 22 Jan 2019 17:22:08 -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 55703 invoked by uid 48); 22 Jan 2019 17:22:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84774] [meta-bug] bogus/missing -Wrestrict
Date: Tue, 22 Jan 2019 17:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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: bug_status resolution
Message-ID: <bug-84774-4-Cpu2OULp2M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84774-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: 2019-01/txt/msg03138.txt.bz2
Content-length: 481

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84774
Bug 84774 depends on bug 88973, which changed state.

Bug 88973 Summary: [8/9 Regression] New -Wrestrict warning since r268048
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88973

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID
>From gcc-bugs-return-630330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:22:09 2019
Return-Path: <gcc-bugs-return-630330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63220 invoked by alias); 22 Jan 2019 17:22:09 -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 54635 invoked by uid 48); 22 Jan 2019 17:22:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88973] [8/9 Regression] New -Wrestrict warning since r268048
Date: Tue, 22 Jan 2019 17:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88973-4-YUqSkullgk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88973-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: 2019-01/txt/msg03139.txt.bz2
Content-length: 2988

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
I've created a test case using the canonicalize_pathname function showing that
it does, in fact, cause an overlap to take place.  The following line in the
output of the test case

  strcpy (0x217f265 = "//bar", 0x217f267 = "bar"): 3

shows that strcpy is being called to copy the 4 bytes "bar\0" from 0x217f267 to
0x217f265, with the last two bytes of the copy overlapping its first two bytes.

$ cat canonicalize_pathname.c && gcc -DPATHNAME='"/foo///bar"' -O2 -Wall
canonicalize_pathname.c && ./a.out
char*
strcpy (char *d, const char *s)
{
  unsigned n = __builtin_strlen (s);
  __builtin_printf ("%s (%p = \"%s\", %p = \"%s\"): %u\n",
                    __func__, d, d, s, s, n);
  __builtin_memcpy (d, s, n + 1);
  return d;
}

char *
canonicalize_pathname (char *path)
{
  int i, start;
  char stub_char, *result;

  result = __builtin_strdup( path );

  stub_char = (*path == '/') ? '/' : '.';

  i = 0;
  while (result[i]) {
    while (result[i] != '\0' && result[i] != '/')
      i++;

    start = i++;

    if (!result[start])
      break;

    while (result[i] == '/')
      i++;

    if ((start + 1) != i)
      {
        strcpy( result + start + 1, result + i );
        i = start + 1;
      }

    if (start > 0 && result[start - 1] == '\\')
      continue;

    if ((start && !result[i])
        || (result[i] == '.' && !result[i+1])) {
      result[--i] = '\0';
      break;
    }

    if (result[i] == '.') {

      if (result[i + 1] == '/') {
        strcpy( result + i, result + i + 1 );
        i = (start < 0) ? 0 : start;
        continue;
      }

      if (result[i + 1] == '.' &&
          (result[i + 2] == '/' || !result[i + 2])) {
        while (--start > -1 && result[start] != '/')
          ;
        strcpy( result + start + 1, result + i + 2 );
        i = (start < 0) ? 0 : start;
        continue;
      }
    }
  }

  if (!*result) {
    *result = stub_char;
    result[1] = '\0';
  }

  return result;
}


int main (void)
{
  char *p = canonicalize_pathname (PATHNAME);
  __builtin_printf ("%s\n", p);
}
canonicalize_pathname.c: In function â€˜canonicalize_pathnameâ€™:
canonicalize_pathname.c:61:2: warning: â€˜strcpyâ€™ accessing 1 byte at offsets [0,
9223372036854775807] and [0, 9223372036854775807] may overlap 1 byte at offset
0 [-Wrestrict]
   61 |  strcpy( result + start + 1, result + i + 2 );
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
strcpy (0x217f265 = "//bar", 0x217f267 = "bar"): 3
/foo/bar
>From gcc-bugs-return-630334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:25:37 2019
Return-Path: <gcc-bugs-return-630334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12531 invoked by alias); 22 Jan 2019 17:25:37 -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 12169 invoked by uid 48); 22 Jan 2019 17:25:33 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88987] New: [9 Regression] ICE: unexpected expression '(bool)sm' of kind implicit_conv_expr
Date: Tue, 22 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88987-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: 2019-01/txt/msg03143.txt.bz2
Content-length: 3446

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

            Bug ID: 88987
           Summary: [9 Regression] ICE: unexpected expression '(bool)sm'
                    of kind implicit_conv_expr
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
testcase:

int sm;

template <typename T> T
pk () noexcept (sm)
{
  return 0;
}

% g++-9.0.0-alpha20190120 -c b6bdwqbi.cpp
b6bdwqbi.cpp:4:17: error: the value of 'sm' is not usable in a constant
expression
    4 | pk () noexcept (sm)
      |                 ^~
b6bdwqbi.cpp:1:5: note: 'int sm' is not const
    1 | int sm;
      |     ^~
b6bdwqbi.cpp:4:19: internal compiler error: unexpected expression '(bool)sm' of
kind implicit_conv_expr
    4 | pk () noexcept (sm)
      |                   ^
0x8cf4fb cxx_eval_constant_expression
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:4983
0x8d2672 cxx_eval_outermost_constant_expr
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/constexpr.c:5095
0x93ed98 build_noexcept_spec(tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/except.c:1292
0x9b32c5 cp_parser_exception_specification_opt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:25149
0x9acfca cp_parser_direct_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:20751
0x9acfca cp_parser_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:20582
0x9bb4ff cp_parser_init_declarator
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:20092
0x9bf6c4 cp_parser_single_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:28096
0x9bf82e cp_parser_template_declaration_after_parameters
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27688
0x9c019e cp_parser_explicit_template_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27934
0x9c019e cp_parser_template_declaration_after_export
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:27953
0x9c2d39 cp_parser_declaration
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:13122
0x9c33a0 cp_parser_translation_unit
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:4698
0x9c33a0 c_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:41003
0xaccdab c_common_parse_file()
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/c-family/c-opts.c:1155
>From gcc-bugs-return-630333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:25:35 2019
Return-Path: <gcc-bugs-return-630333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12189 invoked by alias); 22 Jan 2019 17:25:34 -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 12131 invoked by uid 48); 22 Jan 2019 17:25:30 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88986] New: [9 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in member_vec_binary_search, at cp/name-lookup.c:1136
Date: Tue, 22 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88986-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: 2019-01/txt/msg03142.txt.bz2
Content-length: 4778

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

            Bug ID: 88986
           Summary: [9 Regression] ICE: tree check: expected tree that
                    contains 'decl minimal' structure, have 'error_mark'
                    in member_vec_binary_search, at cp/name-lookup.c:1136
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
testcase extracted from test/SemaTemplate/cxx1z-using-declaration.cpp from the
clang 7.0.1 testsuite:

template<typename ...T> struct C : T... {
  using typename T::type ...;
  void f() { type value; }
};

% g++-9.0.0-alpha20190120 -std=c++17 -c fw9hmgfi.cpp
fw9hmgfi.cpp:1:32: error: 'T ...' is not a class
    1 | template<typename ...T> struct C : T... {
      |                                ^
fw9hmgfi.cpp:1:32: error: 'T ...' is not a class
fw9hmgfi.cpp: In member function 'void C<T>::f()':
fw9hmgfi.cpp:3:12: internal compiler error: tree check: expected tree that
contains 'decl minimal' structure, have 'error_mark' in
member_vec_binary_search, at cp/name-lookup.c:1136
    3 |   void f() { type value; }
      |            ^
0x7c442d tree_contains_struct_check_failed(tree_node const*,
tree_node_structure_enum, char const*, int, char const*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.c:9985
0x615e3d contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.h:3290
0x615e3d member_vec_binary_search
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:1136
0x615e3d get_class_binding_direct(tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:1233
0xa1e9f6 lookup_field_r
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/search.c:980
0xa1dc7d dfs_walk_all(tree_node*, tree_node* (*)(tree_node*, void*), tree_node*
(*)(tree_node*, void*), void*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/search.c:1420
0xa1de56 lookup_member(tree_node*, tree_node*, int, bool, int,
access_failure_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/search.c:1137
0x96f9e5 get_class_binding
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:4449
0x97470f outer_binding(tree_node*, cxx_binding*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:6327
0x97495f innermost_non_namespace_value(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:6364
0x9ca857 check_template_shadow(tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:4135
0x97bc77 do_pushdecl
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:3072
0x97bc77 pushdecl(tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:3162
0x90234e store_parm_decls
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl.c:15640
0x90234e start_preparsed_function(tree_node*, tree_node*, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/decl.c:15514
0x9bc36f cp_parser_late_parsing_for_member
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:28497
0x99aaf2 cp_parser_class_specifier_1
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:23509
0x99bb18 cp_parser_class_specifier
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:23535
0x99bb18 cp_parser_type_specifier
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:17356
0x99cad0 cp_parser_decl_specifier_seq
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/parser.c:14049
>From gcc-bugs-return-630336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:26:00 2019
Return-Path: <gcc-bugs-return-630336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14379 invoked by alias); 22 Jan 2019 17:25:55 -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 13794 invoked by uid 48); 22 Jan 2019 17:25:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83754] Segmentation fault in regex_search
Date: Tue, 22 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-83754-4-8Nqx1QhHX2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83754-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: 2019-01/txt/msg03145.txt.bz2
Content-length: 402

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
     Ever confirmed|0                           |1
>From gcc-bugs-return-630335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:25:49 2019
Return-Path: <gcc-bugs-return-630335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13700 invoked by alias); 22 Jan 2019 17:25:48 -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 13470 invoked by uid 48); 22 Jan 2019 17:25:44 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88988] New: [8/9 Regression] ICE: Segmentation fault (in lookup_name_real_1)
Date: Tue, 22 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88988-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: 2019-01/txt/msg03144.txt.bz2
Content-length: 4683

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

            Bug ID: 88988
           Summary: [8/9 Regression] ICE: Segmentation fault (in
                    lookup_name_real_1)
           Product: gcc
           Version: 8.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, openmp
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

g++-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
testcase w/ -fopenmp:

template <typename T>
class k6 {
public:
  k6 () : y2 ()
  {
    [&] ()
    {
#pragma omp parallel firstprivate (y2)
      ++ (this)->y2;
    } ();
  }

  T y2;
};

k6<int> v6;

% g++-9.0.0-alpha20190120 -fopenmp -c fsbqsi9o.cpp
fsbqsi9o.cpp: In instantiation of 'k6<T>::k6() [with T = int]':
fsbqsi9o.cpp:16:9:   required from here
fsbqsi9o.cpp:8:39: internal compiler error: Segmentation fault
    8 | #pragma omp parallel firstprivate (y2)
      |                                       ^
0xf9cc9f crash_signal
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/toplev.c:326
0x97af4c tree_check(tree_node*, char const*, int, char const*, tree_code)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.h:3175
0x97af4c lookup_name_real_1
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:6395
0x97af4c lookup_name_real(tree_node*, int, int, bool, int, int)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/name-lookup.c:6529
0x9e1757 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16918
0x9ddfe7 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16862
0x9de50e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:17163
0x9ddfe7 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16862
0x9de50e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:17163
0x9f9d55 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16847
0x9f9d55 tsubst_lambda_expr(tree_node*, tree_node*, int, tree_node*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:18023
0x9e89c8 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:19346
0x9e673f tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:18640
0x9dcb5f tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:17756
0x9dcf9b tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16876
0x9ddfe7 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16862
0x9de50e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:17163
0x9ddfe7 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16862
0x9de50e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:17163
0x9dc54e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/cp/pt.c:16847
>From gcc-bugs-return-630332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:25:20 2019
Return-Path: <gcc-bugs-return-630332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11037 invoked by alias); 22 Jan 2019 17:25:01 -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 10551 invoked by uid 48); 22 Jan 2019 17:24:40 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88985] New: [9 Regression] ICE in estimate_edge_devirt_benefit, at ipa-fnsummary.c:2585
Date: Tue, 22 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88985-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: 2019-01/txt/msg03141.txt.bz2
Content-length: 2170

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

            Bug ID: 88985
           Summary: [9 Regression] ICE in estimate_edge_devirt_benefit, at
                    ipa-fnsummary.c:2585
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Changed between 20180610 and 20180624, at -O0 on x86_64 GNU/Linux :


$ cat z1.c
void f (void)
{
}
__attribute__((__optimize__("O2")))
void g (void f())
{
  f();
}
__attribute__((__optimize__("O2")))
void h (void)
{
  g(f);
}


$ gcc-9-20180610 -c z1.c -O0
$
$ gcc-9-20190120 -c z1.c -O2
$
$ gcc-9-20190120 -c z1.c -O0
during IPA pass: inline
z1.c:13:1: internal compiler error: Segmentation fault
   13 | }
      | ^
0xa8afef crash_signal
        ../../gcc/toplev.c:326
0x8bb89e estimate_edge_devirt_benefit
        ../../gcc/ipa-fnsummary.c:2585
0x8be869 estimate_edge_size_and_time
        ../../gcc/ipa-fnsummary.c:2608
0x8be869 estimate_calls_size_and_time
        ../../gcc/ipa-fnsummary.c:2674
0x8bfc1b estimate_node_size_and_time(cgraph_node*, unsigned int, unsigned int,
vec<tree_node*, va_heap, vl_ptr>, vec<ipa_polymorphic_call_context, va_heap,
vl_ptr>, vec<ipa_agg_jump_function*, va_heap, vl_ptr>, int*, int*, sreal*,
sreal*, int*, vec<inline_param_summary, va_heap, vl_ptr>)
        ../../gcc/ipa-fnsummary.c:2733
0x8cce81 do_estimate_edge_size(cgraph_edge*)
        ../../gcc/ipa-inline-analysis.c:209
0x8cd14f estimate_edge_size
        ../../gcc/ipa-inline.h:75
0x8cd14f estimate_edge_growth
        ../../gcc/ipa-inline.h:86
0x8cd14f do_estimate_growth_1
        ../../gcc/ipa-inline-analysis.c:312
0x8cd1fe cgraph_node::call_for_symbol_and_aliases(bool (*)(cgraph_node*,
void*), void*, bool)
        ../../gcc/cgraph.h:3241
0x8cd1fe estimate_growth(cgraph_node*)
        ../../gcc/ipa-inline-analysis.c:326
0x11f9758 inline_small_functions
        ../../gcc/ipa-inline.c:1792
0x11f9758 ipa_inline
        ../../gcc/ipa-inline.c:2528
0x11f9758 execute
        ../../gcc/ipa-inline.c:2936
>From gcc-bugs-return-630337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:26:14 2019
Return-Path: <gcc-bugs-return-630337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15280 invoked by alias); 22 Jan 2019 17:26:14 -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 15194 invoked by uid 48); 22 Jan 2019 17:26:10 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Tue, 22 Jan 2019 17:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-rVJUE65bRb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03146.txt.bz2
Content-length: 718

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

--- Comment #22 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Steve Ellcey from comment #21)
> If I look at this specific example:
> 
> int f2 (int x, int y)
> {
>   return (x & ~0x0ff000) | ((y & 0x0ff) << 12);
> }
> 

> Is this because of x0 (a hard register) at the destination in insn 15?

Yes, the hard reg change affects the rtl shape in these tests so it fails to
match in combine. I have a simple fix for the tst_5 and tst_6 failures.

You can check this by ensuring there are no hard registers in the test:

int f2a (int x, int y)
{
   x++;
   y++;
   return (x & ~0x0ff000) | ((y & 0x0ff) << 12);
}

This also fails to match before r265398.
>From gcc-bugs-return-630338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:28:29 2019
Return-Path: <gcc-bugs-return-630338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18075 invoked by alias); 22 Jan 2019 17:28:29 -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 17530 invoked by uid 48); 22 Jan 2019 17:28:24 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88989] New: ICE in resolvePropertiesX, at d/dmd/expression.c:251
Date: Tue, 22 Jan 2019 17:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-88989-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: 2019-01/txt/msg03147.txt.bz2
Content-length: 2358

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

            Bug ID: 88989
           Summary: ICE in resolvePropertiesX, at d/dmd/expression.c:251
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

With following test :


$ cat z1.d
struct A
{
  int i = A();
};


$ gdc-9-20190120 -c z1.d
d21: internal compiler error: Segmentation fault
0xb821cf crash_signal
        ../../gcc/toplev.c:326
0x6ac417 resolvePropertiesX(Scope*, Expression*, Expression*)
        ../../gcc/d/dmd/expression.c:251
0x6ace7f resolveProperties(Scope*, Expression*)
        ../../gcc/d/dmd/expression.c:496
0x6b5490 preFunctionParameters
        ../../gcc/d/dmd/expressionsem.c:97
0x6c64ad preFunctionParameters
        ../../gcc/d/dmd/expressionsem.c:89
0x6c64ad ExpressionSemanticVisitor::visit(CallExp*)
        ../../gcc/d/dmd/expressionsem.c:2930
0x6b57a5 semantic(Expression*, Scope*)
        ../../gcc/d/dmd/expressionsem.c:8166
0x6e5b9d InitializerSemanticVisitor::visit(ExpInitializer*)
        ../../gcc/d/dmd/initsem.c:348
0x6e583b semantic(Initializer*, Scope*, Type*, NeedInterpret)
        ../../gcc/d/dmd/initsem.c:520
0x65c57c VarDeclaration::getConstInitializer(bool)
        ../../gcc/d/dmd/declaration.c:1966
0x683c46 AggregateDeclaration::fill(Loc, Array<Expression*>*, bool)
        ../../gcc/d/dmd/dstruct.c:726
0x6b8bf4 ExpressionSemanticVisitor::visit(StructLiteralExp*)
        ../../gcc/d/dmd/expressionsem.c:776
0x6c805b StructLiteralExp::accept(Visitor*)
        ../../gcc/d/dmd/expression.h:490
0x6c805b semantic(Expression*, Scope*)
        ../../gcc/d/dmd/expressionsem.c:8166
0x6c805b ExpressionSemanticVisitor::visit(CallExp*)
        ../../gcc/d/dmd/expressionsem.c:3006
0x6b57a5 semantic(Expression*, Scope*)
        ../../gcc/d/dmd/expressionsem.c:8166
0x6e5b9d InitializerSemanticVisitor::visit(ExpInitializer*)
        ../../gcc/d/dmd/initsem.c:348
0x6e583b semantic(Initializer*, Scope*, Type*, NeedInterpret)
        ../../gcc/d/dmd/initsem.c:520
0x659133 VarDeclaration::semantic2(Scope*)
        ../../gcc/d/dmd/declaration.c:1619
0x683187 AggregateDeclaration::semantic2(Scope*)
        ../../gcc/d/dmd/dstruct.c:267
>From gcc-bugs-return-630339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:29:45 2019
Return-Path: <gcc-bugs-return-630339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51394 invoked by alias); 22 Jan 2019 17:29:45 -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 49248 invoked by uid 48); 22 Jan 2019 17:29:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86164] std::regex crashes when matching long lines
Date: Tue, 22 Jan 2019 17:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86164-4-IzXPbUvmWE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86164-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86164-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: 2019-01/txt/msg03148.txt.bz2
Content-length: 402

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
     Ever confirmed|0                           |1
>From gcc-bugs-return-630340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:30:58 2019
Return-Path: <gcc-bugs-return-630340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69369 invoked by alias); 22 Jan 2019 17:30:56 -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 69305 invoked by uid 48); 22 Jan 2019 17:30:51 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88990] New: ICE in get_symbol_decl, at d/decl.cc:1097
Date: Tue, 22 Jan 2019 17:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-88990-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: 2019-01/txt/msg03149.txt.bz2
Content-length: 1356

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

            Bug ID: 88990
           Summary: ICE in get_symbol_decl, at d/decl.cc:1097
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

With an invalid qualifier :


$ cat z1.d
class A
{
  extern
  {
    void f() { }
  }
}


$ gdc-9-20190120 -c z1.d
z1.d: In function 'f':
z1.d:1:1: internal compiler error: in get_symbol_decl, at d/decl.cc:1097
    1 | class A
      | ^
0x777318 get_symbol_decl(Declaration*)
        ../../gcc/d/decl.cc:1097
0x77957d get_symbol_decl(Declaration*)
        ../../gcc/d/decl.cc:904
0x77957d DeclVisitor::visit(FuncDeclaration*)
        ../../gcc/d/decl.cc:798
0x7788b7 DeclVisitor::visit(AttribDeclaration*)
        ../../gcc/d/decl.cc:222
0x779b27 DeclVisitor::visit(ClassDeclaration*)
        ../../gcc/d/decl.cc:436
0x7765b1 build_decl_tree(Dsymbol*)
        ../../gcc/d/decl.cc:949
0x782a30 build_module_tree(Module*)
        ../../gcc/d/modules.cc:717
0x7789eb DeclVisitor::visit(Module*)
        ../../gcc/d/decl.cc:142
0x7765b1 build_decl_tree(Dsymbol*)
        ../../gcc/d/decl.cc:949
0x773990 d_parse_file()
        ../../gcc/d/d-lang.cc:1278
>From gcc-bugs-return-630341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:37:28 2019
Return-Path: <gcc-bugs-return-630341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79029 invoked by alias); 22 Jan 2019 17:37:27 -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 78739 invoked by uid 48); 22 Jan 2019 17:37:23 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88981] [nvptx, openacc, libgomp] How to handle async regions without corresponding wait
Date: Tue, 22 Jan 2019 17:37: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88981-4-Jq3BDxtW3b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88981-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: 2019-01/txt/msg03150.txt.bz2
Content-length: 598

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
A good thing to note here, when adding #pragma acc wait, the program (compiled
with -O0) takes ~10 seconds to finish on my quadro 1200m.

Without the pragma acc wait, it still takes 10 seconds.

When inspecting with a debugger where it's waiting (since there's no wait
reponsible for this), we're hanging on either cuMemFree or cuCtxDestroy.  I
can't find documentation of this hanging behaviour, so this behaviour may be
specific to the driver version or card or architecture.
>From gcc-bugs-return-630342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:50:31 2019
Return-Path: <gcc-bugs-return-630342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118548 invoked by alias); 22 Jan 2019 17:50:31 -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 118417 invoked by uid 55); 22 Jan 2019 17:50:26 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Tue, 22 Jan 2019 17:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-fIz7vtOjEN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03151.txt.bz2
Content-length: 726

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

--- Comment #23 from Wilco <wilco at gcc dot gnu.org> ---
Author: wilco
Date: Tue Jan 22 17:49:46 2019
New Revision: 268159

URL: https://gcc.gnu.org/viewcvs?rev=268159&root=gcc&view=rev
Log:
Fix vect-nop-move.c test

Fix a failing test - changes in Combine mean the test now fails
eventhough the generated code is the same.  Given there are several
AArch64-specific tests for vec-select, remove the scanning of Combine
output.  Committed as trivial fix.

    testsuite/
        PR rtl-optimization/87763
        * gcc.dg/vect/vect-nop-move.c: Fix testcase on AArch64.

Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gcc.dg/vect/vect-nop-move.c
>From gcc-bugs-return-630343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:50:50 2019
Return-Path: <gcc-bugs-return-630343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119449 invoked by alias); 22 Jan 2019 17:50: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 119355 invoked by uid 48); 22 Jan 2019 17:50:46 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80257] Cygwin test fail: pointer_check_1.f90 output test
Date: Tue, 22 Jan 2019 17:50: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: 7.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
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_status resolution
Message-ID: <bug-80257-4-UqoOVIcOK5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80257-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: 2019-01/txt/msg03152.txt.bz2
Content-length: 473

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
No feedback, closing as WORKSFORME.
>From gcc-bugs-return-630344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:52:12 2019
Return-Path: <gcc-bugs-return-630344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123601 invoked by alias); 22 Jan 2019 17:52:11 -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 123476 invoked by uid 48); 22 Jan 2019 17:52:06 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57297] FAIL: gfortran.dg/select_type_4.f90 -O2  execution test
Date: Tue, 22 Jan 2019 17:52: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.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
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_status resolution
Message-ID: <bug-57297-4-3yJNASKJKs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57297-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57297-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: 2019-01/txt/msg03153.txt.bz2
Content-length: 474

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #12 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
No feedback, closing as WORKSFORME.
>From gcc-bugs-return-630345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:53:58 2019
Return-Path: <gcc-bugs-return-630345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3883 invoked by alias); 22 Jan 2019 17:53:55 -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 3821 invoked by uid 48); 22 Jan 2019 17:53:51 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/39795] Support round-to-zero in Fortran front-end
Date: Tue, 22 Jan 2019 17:53: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.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
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_status resolution
Message-ID: <bug-39795-4-i2WOVVSao3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-39795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-39795-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: 2019-01/txt/msg03154.txt.bz2
Content-length: 467

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
No feedback, closing as WONTFIX.
>From gcc-bugs-return-630347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:56:46 2019
Return-Path: <gcc-bugs-return-630347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37319 invoked by alias); 22 Jan 2019 17:56:45 -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 37222 invoked by uid 89); 22 Jan 2019 17:56:45 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: =?ISO-8859-1?Q?Yes, score=6.3 required=5.0 testsºYES_50,BODY_8BITS,GARBLED_BODY,GIT_PATCH_3,HK_RANDOM_ENVFROM,HTML_MESSAGE,KAM_LAZY_DOMAIN_SECURITY,MISSING_MID,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_XBL autolearn=no version=3.3.2 spammy=Hx-spam-relays-external:SKY-20150219JSJ, H*RU:SKY-20150219JSJ, H*r:SKY-20150219JSJ, æ£?X-HELO: xqwz.com
Received: from Unknown (HELO xqwz.com) (114.99.11.100) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 22 Jan 2019 17:56:44 +0000
Received: from SKY-20150219JSJ ([127.0.0.1]) by localhost via TCP with ESMTPA; Wed, 23 Jan 2019 01:56:31 +0800
MIME-Version: 1.0
From: hpefmjdkv <hpefmjdkv@xqwz.com>
Sender: hpefmjdkv <hpefmjdkv@xqwz.com>
To: gcc-bugs@gcc.gnu.org
Date: Tue, 22 Jan 2019 17:56:00 -0000
Subject: =?utf-8?B?YUdP5o+QLy/kvpsvL+eojiUl5qCXLy8=?Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-SW-Source: 2019-01/txt/msg03156.txt.bz2
Content-length: 452

Z2NjLWJ1Z3NAZ2NjLmdudS5vcmcNCisrKysrKysrKysrKysrKysrKysrKysr
KysrKysrDQrmsI/nkZrkvJgg5oOgIOWKniDnkIYg5q2jIOinhCDnqI4g56Wo
77yM6K6kIOivgSDlkI4g5LuYJm5ic3A7IOasvuOAgg0KJm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IOivpiZuYnNwOyZuYnNwOyDnlLXvvJrmnY4g
55Sf77yMMTM24oCUNjA3NeKAlCA0MTkw77yMDQombmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsg5LiaJm5ic3A7Jm5ic3A7IHHvvJoxNTfi
gJQgNTMz4oCUIDI2OTgNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0NCg=>From gcc-bugs-return-630346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:56:39 2019
Return-Path: <gcc-bugs-return-630346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35204 invoked by alias); 22 Jan 2019 17:56:39 -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 30430 invoked by uid 55); 22 Jan 2019 17:56:35 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88469] [7/8 regression] AAPCS - Struct with 64-bit bitfield may be passed in wrong registers
Date: Tue, 22 Jan 2019 17:56: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: 8.2.0
X-Bugzilla-Keywords: ABI, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88469-4-5o8qL6gUKR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88469-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88469-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: 2019-01/txt/msg03155.txt.bz2
Content-length: 1091

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

--- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Tue Jan 22 17:56:02 2019
New Revision: 268160

URL: https://gcc.gnu.org/viewcvs?rev=268160&root=gcc&view=rev
Log:
[arm] Further fixes for PR88469

A bitfield that is exactly the same size as an integral type and
naturally aligned will have DECL_BIT_FIELD cleared.  So we need to
check DECL_BIT_FIELD_TYPE to be sure whether or not the underlying
type was declared with a bitfield declaration.

I've also added a test for bitfields that are based on overaligned types.

        PR target/88469
gcc:
        * config/arm/arm.c (arm_needs_double_word_align): Check
        DECL_BIT_FIELD_TYPE.

gcc/testsuite:
        * gcc.target/arm/aapcs/bitfield2.c: New test.
        * gcc.target/arm/aapcs/bitfield3.c: New test.


Added:
    trunk/gcc/testsuite/gcc.target/arm/aapcs/bitfield2.c
    trunk/gcc/testsuite/gcc.target/arm/aapcs/bitfield3.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/arm/arm.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 17:57:42 2019
Return-Path: <gcc-bugs-return-630348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74059 invoked by alias); 22 Jan 2019 17:57:41 -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 73927 invoked by uid 48); 22 Jan 2019 17:57:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88967] [9 regression] openmp default(none) broken
Date: Tue, 22 Jan 2019 17:57: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
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-88967-4-VQQEDve3xc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88967-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: 2019-01/txt/msg03157.txt.bz2
Content-length: 861

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

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
firstprivate is that each thread will have its own copy of the variable,
initialized from the original.
shared means there is just one copy.
E.g. if you take the address of the variable within the region, for
firstprivate each thread will have different, typically it will be a stack slot
in the outlined function, while for shared it will need to live either in the
structure used to pass data around, or worse address of that variable will be
passed in that structure.  While e.g. some recent versions of gcc try to
optimize
certain cases of shared into firstprivate, see e.g. PR68128 (or for
non-addressable non-reference const vars it was done even much earlier), that
is just an optimization not every compiler will do for you.
>From gcc-bugs-return-630349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:03:45 2019
Return-Path: <gcc-bugs-return-630349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86237 invoked by alias); 22 Jan 2019 18:03:45 -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 86195 invoked by uid 48); 22 Jan 2019 18:03:41 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88991] New: missing warning on a strcpy and strlen from a zero-length array
Date: Tue, 22 Jan 2019 18:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88991-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: 2019-01/txt/msg03158.txt.bz2
Content-length: 1594

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

            Bug ID: 88991
           Summary: missing warning on a strcpy and strlen from a
                    zero-length array
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

GCC diagnoses the undefined behavior in function f() in the test case below but
fails to diagnose the same bug in g() or h().

However, the warning issued for f() should be (also) for the call to strlen(s)
which is also undefined.  Worse, in g() neither the call to strlen(s) nor
memcpy() is diagnosed.

$ cat t.c && gcc -O2 -S -Wall t.c

void f (char *d)
{
  __builtin_memcpy (d, s, __builtin_strlen (s) + 1);
}

void g (char *d)
{
  unsigned n = __builtin_strlen (s) + 1;   // missing warning
  __builtin_memcpy (d, s, n);              // same here
}

void h (char *d)
{
  __builtin_strcpy (d, s);                 // missing warning here too
}
t.c: In function â€˜fâ€™:
t.c:5:3: warning: â€˜__builtin_memcpyâ€™ forming offset [1, 9223372036854775805] is
out of the bounds [0, 0] of object â€˜sâ€™ with type â€˜const char[]â€™
[-Warray-bounds]
    5 |   __builtin_memcpy (d, s, __builtin_strlen (s) + 1);
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c:1:12: note: â€˜sâ€™ declared here
    1 | const char s[0] = { };
      |            ^
>From gcc-bugs-return-630350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:04:55 2019
Return-Path: <gcc-bugs-return-630350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109177 invoked by alias); 22 Jan 2019 18:04:52 -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 106998 invoked by uid 48); 22 Jan 2019 18:04:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88991] missing warning on a strcpy and strlen from a zero-length array
Date: Tue, 22 Jan 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords see_also
Message-ID: <bug-88991-4-uL1k0gHS45@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88991-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88991-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: 2019-01/txt/msg03159.txt.bz2
Content-length: 584

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=88956

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
This was noticed while adding a test case for the fix for bug 88956.
>From gcc-bugs-return-630351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:08:24 2019
Return-Path: <gcc-bugs-return-630351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119586 invoked by alias); 22 Jan 2019 18:08:23 -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 119528 invoked by uid 48); 22 Jan 2019 18:08:20 -0000
From: "19Sebastian95 at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88979] [C++20] P0634R3 not working for constructor parameter types
Date: Tue, 22 Jan 2019 18:08: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 19Sebastian95 at gmx dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88979-4-im8GLbCURx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88979-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88979-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: 2019-01/txt/msg03160.txt.bz2
Content-length: 979

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

--- Comment #2 from 19Sebastian95 at gmx dot de ---
I'm sorry if I'm misinterpreting this, but the program I wrote does compile
with gcc 9.0, as the "error" part is commented out, so I'll just write what to
do to get the descriped error: 

If my constructor is:

A(typename T::type a) : mA{a} {} 

it is working, but if I remove the typename it'll give me The "error: expected
')' before 'a'" error. (As far as I know it should detect that it is only a
missing typename, so for versions before c++20 it should be "error: need
'typename' [...]" and for c++20 it shouldn't be an error).

So right now this won't compile:
A(T::type a) : mA{a} {} 

But if I'd define the constructor out-of-line it won't give me an error:

template<typename T>
A<T>::A(T::type a) : mA{a} {} 

As GCC is detecting that there can only be a type at this position, which it
doesn't with the "header-only"-version.

I hope this will help.
>From gcc-bugs-return-630352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:17:29 2019
Return-Path: <gcc-bugs-return-630352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29288 invoked by alias); 22 Jan 2019 18:17:28 -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 29191 invoked by uid 48); 22 Jan 2019 18:17:23 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88992] New: missing -Warray-bounds indexing into a zero-length array
Date: Tue, 22 Jan 2019 18:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88992-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: 2019-01/txt/msg03161.txt.bz2
Content-length: 1758

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

            Bug ID: 88992
           Summary: missing -Warray-bounds indexing into a zero-length
                    array
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

Also while adding a test for the fix for bug 88956 I noticed that GCC doesn't
diagnose indexing into zero-length arrays.  The out-of-bounds accesses to the
global zero-length arrays are folded to zero while those to the local ones are
emitted.

$ gcc -O2 -S -Wall t.c
const char s1[1] = { };
int f1 (void)
{
  return s1[3];   // -Warray-bounds (good)
}

const char s0[0] = { };
int f0 (void)
{
  return s0[3];   // missing warning
}


int g1 (void)
{
  const char s1[1] = { };
  return s1[3];   // -Warray-bounds (good)
}

int g0 (void)
{
  const char s0[0] = { };
  return s0[3];   // missing warning
}

t.c: In function â€˜f1â€™:
t.c:4:12: warning: array subscript 3 is above array bounds of â€˜const char[1]â€™
[-Warray-bounds]
    4 |   return s1[3];   // -Warray-bounds (good)
      |          ~~^~~
t.c:1:12: note: while referencing â€˜s1â€™
    1 | const char s1[1] = { };
      |            ^~
t.c: In function â€˜g1â€™:
t.c:17:12: warning: array subscript 3 is above array bounds of â€˜const char[1]â€™
[-Warray-bounds]
   17 |   return s1[3];   // -Warray-bounds (good)
      |          ~~^~~
t.c:16:14: note: while referencing â€˜s1â€™
   16 |   const char s1[1] = { };
      |              ^~
>From gcc-bugs-return-630353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:28:16 2019
Return-Path: <gcc-bugs-return-630353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47322 invoked by alias); 22 Jan 2019 18:28:16 -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 47280 invoked by uid 48); 22 Jan 2019 18:28:12 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88991] missing warning on a strcpy and strlen from a zero-length array
Date: Tue, 22 Jan 2019 18:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: blocked
Message-ID: <bug-88991-4-i2LwAflcyb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88991-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88991-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: 2019-01/txt/msg03162.txt.bz2
Content-length: 718

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |88443

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The most appropriate warning in all these cases is probably -Wstringop-overflow
rather than -Warray-bounds, since the former is meant to diagnose both writing
and reading past the end of an array by string functions.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
[Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
>From gcc-bugs-return-630355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:29:33 2019
Return-Path: <gcc-bugs-return-630355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50772 invoked by alias); 22 Jan 2019 18:29:33 -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 50073 invoked by uid 48); 22 Jan 2019 18:29:29 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88347] ICE in begin_move_insn, at sched-ebb.c:175
Date: Tue, 22 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm 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:
Message-ID: <bug-88347-4-Gmm6Xgp7DB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88347-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88347-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: 2019-01/txt/msg03164.txt.bz2
Content-length: 184

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

--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
*** Bug 88423 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-630354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:29:33 2019
Return-Path: <gcc-bugs-return-630354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50155 invoked by alias); 22 Jan 2019 18:29:32 -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 49993 invoked by uid 48); 22 Jan 2019 18:29:28 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88423] [9 Regression] ICE in begin_move_insn, at sched-ebb.c:175
Date: Tue, 22 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88423-4-pX4XILpKP4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88423-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: 2019-01/txt/msg03163.txt.bz2
Content-length: 669

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #6)
> Is this a dup of PR88347?

Looks like it, and your fix there looks better (it fixes both).  I'm trying a
bootstrap of your fix.

*** This bug has been marked as a duplicate of bug 88347 ***
>From gcc-bugs-return-630356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:36:50 2019
Return-Path: <gcc-bugs-return-630356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76786 invoked by alias); 22 Jan 2019 18:36: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 76493 invoked by uid 48); 22 Jan 2019 18:36:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88984] [9 Regression] ICE in genericize_switch_stmt, at cp/cp-gimplify.c:377
Date: Tue, 22 Jan 2019 18:36: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88984-4-ZXPZp4Vd0J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88984-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: 2019-01/txt/msg03165.txt.bz2
Content-length: 253

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45498
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45498&action=edit
gcc9-pr88984.patch

Untested fix.
>From gcc-bugs-return-630357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 18:40:19 2019
Return-Path: <gcc-bugs-return-630357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80610 invoked by alias); 22 Jan 2019 18:40:18 -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 80527 invoked by uid 48); 22 Jan 2019 18:40:14 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88963] gcc generates terrible code for vectors of 64+ length which are not natively supported
Date: Tue, 22 Jan 2019 18:40: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
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:
Message-ID: <bug-88963-4-MiD7y0sVqF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88963-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: 2019-01/txt/msg03166.txt.bz2
Content-length: 257

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

--- Comment #10 from Devin Hussey <husseydevin at gmail dot com> ---
I also want to add that aarch64 shouldn't even be spilling; it has 32 NEON
registers and with 128 byte vectors it should only use 24.
>From gcc-bugs-return-630358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 19:06:20 2019
Return-Path: <gcc-bugs-return-630358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84518 invoked by alias); 22 Jan 2019 19:06: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 84472 invoked by uid 48); 22 Jan 2019 19:06:16 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88347] ICE in begin_move_insn, at sched-ebb.c:175
Date: Tue, 22 Jan 2019 19:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88347-4-xSw85uR9SF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88347-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88347-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: 2019-01/txt/msg03167.txt.bz2
Content-length: 590

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |dmalcolm at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |dmalcolm at gcc dot gnu.org

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Segher's fix appears superior to mine; am testing it now...
>From gcc-bugs-return-630359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 19:07:39 2019
Return-Path: <gcc-bugs-return-630359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103838 invoked by alias); 22 Jan 2019 19:07:39 -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 103674 invoked by uid 48); 22 Jan 2019 19:07:35 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88989] ICE in resolvePropertiesX, at d/dmd/expression.c:251
Date: Tue, 22 Jan 2019 19:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88989-4-y9rWgQrMVN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88989-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88989-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: 2019-01/txt/msg03168.txt.bz2
Content-length: 171

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

--- Comment #1 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Thanks.

Out of curiosity, are you fuzz testing?
>From gcc-bugs-return-630360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 19:12:42 2019
Return-Path: <gcc-bugs-return-630360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128012 invoked by alias); 22 Jan 2019 19:12:42 -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 127916 invoked by uid 48); 22 Jan 2019 19:12:36 -0000
From: "kelvin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88497] Improve Accumulation in Auto-Vectorized Code
Date: Tue, 22 Jan 2019 19:12: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kelvin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88497-4-bEtOGD71vw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88497-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88497-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: 2019-01/txt/msg03169.txt.bz2
Content-length: 709

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

--- Comment #7 from kelvin at gcc dot gnu.org ---
Here is the original program that motivated my simplified reproducer:

extern void first_dummy ();
extern void dummy (double sacc, int n);
extern void other_dummy ();

extern float opt_value;
extern char *opt_desc;

#define M 128
#define N 512

double x [N];
double y [N];

int main (int argc, char *argv []) {
  double sacc;

  first_dummy ();
  for (int j = 0; j < M; j++) {

    sacc = 0.00;
    for (unsigned long long int i = 0; i < N; i++) {
      sacc += x[i] * y[i];
    }
    dummy (sacc, N);
  }
  opt_value = ((float) N) * 2 * ((float) M);
  opt_desc = "flops";
  other_dummy ();
}
>From gcc-bugs-return-630361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 19:21:31 2019
Return-Path: <gcc-bugs-return-630361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12420 invoked by alias); 22 Jan 2019 19:21:30 -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 12326 invoked by uid 48); 22 Jan 2019 19:21:26 -0000
From: "rjones at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88993] New: GCC 9 -Wformat-overflow=2 should reflect real libc limits
Date: Tue, 22 Jan 2019 19:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rjones at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88993-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: 2019-01/txt/msg03170.txt.bz2
Content-length: 1835

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

            Bug ID: 88993
           Summary: GCC 9 -Wformat-overflow=2 should reflect real libc
                    limits
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rjones at redhat dot com
  Target Milestone: ---

-Wformat-overflow=2 is the default when using gnulib manywarnings.m4, and
so is used by a bunch of GNU projects.  I've found with GCC 9 it is very
aggressive warning about any string it statically determine could be
longer than 4095 characters (see
https://stackoverflow.com/questions/8119914/printf-fprintf-maximum-size-according-to-c99?rq=1
for the presumed origin of that limit).

I am using a libc which does not have such a small limit (in fact, I believe
it's unlimited) and I think this warning should warn about the real
toolchain limit, not some peculiar corner of the C99 standard that vanishingly
small number of libcs are really limited by (and if they are - fix your libc).

Example below:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

int
main (void)
{
  char s[4097];

  fgets (s, sizeof s, stdin);
  printf ("%.*s", (int) strlen (s), s);

//test.c:11:12: warning: â€˜%.*sâ€™ directive output between 0 and 4096 bytes may
exceed minimum required size of 4095 [-Wformat-overflow=]
//   11 |   printf ("%.*s", (int) strlen (s), s);
//      |            ^~~~                     ~

  printf ("%s", s);

//test.c:12:12: warning: â€˜%sâ€™ directive output between 0 and 4096 bytes may
exceed minimum required size of 4095 [-Wformat-overflow=]
//   12 |   printf ("%s", s);
//      |            ^~   ~

  exit (0);
}
>From gcc-bugs-return-630362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 19:22:57 2019
Return-Path: <gcc-bugs-return-630362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15775 invoked by alias); 22 Jan 2019 19:22:57 -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 15716 invoked by uid 48); 22 Jan 2019 19:22:53 -0000
From: "rjones at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88993] GCC 9 -Wformat-overflow=2 should reflect real libc limits
Date: Tue, 22 Jan 2019 19:22: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rjones at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88993-4-exsRlYgRbe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88993-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: 2019-01/txt/msg03171.txt.bz2
Content-length: 185

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

--- Comment #1 from Richard W.M. Jones <rjones at redhat dot com> ---
Sorry, forgot the version.  It's:

gcc-9.0.0-0.3.fc30.x86_64
>From gcc-bugs-return-630363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 19:57:26 2019
Return-Path: <gcc-bugs-return-630363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72048 invoked by alias); 22 Jan 2019 19:57:25 -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 72007 invoked by uid 48); 22 Jan 2019 19:57:21 -0000
From: "wieichdashasse at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87999] Constexpr eval. in static_assert makes string_view comparison non constexpr
Date: Tue, 22 Jan 2019 19:57: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wieichdashasse at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-87999-4-aDz5SJBxAJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87999-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87999-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: 2019-01/txt/msg03172.txt.bz2
Content-length: 513

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

Justin Meyer <wieichdashasse at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Justin Meyer <wieichdashasse at gmail dot com> ---
This seems to be fixed in trunk. can't seem to find the commit that fixed it
though.
>From gcc-bugs-return-630364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 20:34:24 2019
Return-Path: <gcc-bugs-return-630364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8683 invoked by alias); 22 Jan 2019 20:34:23 -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 8632 invoked by uid 48); 22 Jan 2019 20:34:19 -0000
From: "moussu.robin at pm dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] New: [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Tue, 22 Jan 2019 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: moussu.robin at pm dot me
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88994-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: 2019-01/txt/msg03173.txt.bz2
Content-length: 3085

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

            Bug ID: 88994
           Summary: [GCOV] encoding (or unicode) error with gcov/gcc9 when
                    generating filename
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: moussu.robin at pm dot me
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Hello,

I filled first a bug on gcovr bug-tracker, and they eventually redirected me
here.

https://github.com/gcovr/gcovr/issues/292

All steps to reproduce the bug (and a lot of details on the output of the
various commands I run is present on the above link.

gcov is trying to create a filename with an extremely strange name: '
pn+\x89\x7f' (with a leading space, and invalid unicode sequence).

Here is a sum-up of what I think is relevant to gcov. Fell free to ask me any
additional details.

```
âžœ  $ gcov --version
gcov (GCC) 9.0.0 20190107 (experimental)
âžœ  $ gcc --version
gcc (GCC) 9.0.0 20190107 (experimental)

âžœ  $ locale
LANG=fr_FR.UTF-8
LC_CTYPE=fr_FR.UTF-8
LC_NUMERIC="fr_FR.UTF-8"
LC_TIME="fr_FR.UTF-8"
LC_COLLATE="fr_FR.UTF-8"
LC_MONETARY="fr_FR.UTF-8"
LC_MESSAGES="fr_FR.UTF-8"
LC_PAPER="fr_FR.UTF-8"
LC_NAME="fr_FR.UTF-8"
LC_ADDRESS="fr_FR.UTF-8"
LC_TELEPHONE="fr_FR.UTF-8"
LC_MEASUREMENT="fr_FR.UTF-8"
LC_IDENTIFICATION="fr_FR.UTF-8"
LC_ALL=
```

```
âžœ  $ gcov
/home/robin/dev/meson-sample-project/build/third_party/src/baz/6798489@@baz@sta/baz.cc.gcno
--branch-counts --branch-probabilities --preserve-paths --object-directory
/home/robin/dev/meson-sample-project/build/third_party/src/baz/6798489@@baz@sta
/home/robin/dev/meson-sample-project/build/third_party/src/baz/6798489@@baz@sta/baz.cc.gcda:
ne peut ouvrir le fichier de donnÃ©es, supposÃ© non exÃ©cutÃ©
File Â« ../third_party/src/baz/baz.cc Â»
Lignes exÃ©cutÃ©es: 0.00% sur 1
Pas de branchement
Pas d'appel
Impossible d'ouvrir le fichier de sortie Â«  Â»

File Â« /usr/include/c++/9.0.0/iostream Â»
Aucune ligne exÃ©cutable
Pas de branchement
Pas d'appel
Suppression de Â«  Â»
```

Notice the difference when I'm using `LANG=C` in the filename.

```
âžœ  $ LANG=C gcov
/home/robin/dev/meson-sample-project/build/third_party/src/baz/6798489@@baz@sta/baz.cc.gcno
--branch-counts --branch-probabilities --preserve-paths --object-directory
/home/robin/dev/meson-sample-project/build/third_party/src/baz/6798489@@baz@sta
/home/robin/dev/meson-sample-project/build/third_party/src/baz/6798489@@baz@sta/baz.cc.gcda:cannot
open data file, assuming not executed
File '../third_party/src/baz/baz.cc'
Lines executed:0.00% of 1
No branches
No calls
Creating '@ï¿½Ù®'
Cannot open source file ../third_party/src/baz/baz.cc

File '/usr/include/c++/9.0.0/iostream'
No executable lines
No branches
No calls
Removing 'ï¿½Ù®'
```
>From gcc-bugs-return-630365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 21:19:22 2019
Return-Path: <gcc-bugs-return-630365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12765 invoked by alias); 22 Jan 2019 21:19:22 -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 9926 invoked by uid 48); 22 Jan 2019 21:19:16 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57553] [F08] Valid use of STORAGE_SIZE rejected, bad error message for invalid use
Date: Tue, 22 Jan 2019 21:19: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.9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
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:
Message-ID: <bug-57553-4-dluknp66Mo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57553-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57553-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: 2019-01/txt/msg03174.txt.bz2
Content-length: 197

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

--- Comment #7 from Harald Anlauf <anlauf at gmx dot de> ---
Patch submitted for review:

https://gcc.gnu.org/ml/fortran/2019-01/msg00201.html
>From gcc-bugs-return-630366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 21:25:08 2019
Return-Path: <gcc-bugs-return-630366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45275 invoked by alias); 22 Jan 2019 21:24: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 45029 invoked by uid 55); 22 Jan 2019 21:24:31 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88579] Calculating power of powers of two
Date: Tue, 22 Jan 2019 21:24: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88579-4-jJdRaLswub@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88579-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88579-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: 2019-01/txt/msg03175.txt.bz2
Content-length: 728

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

--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Tue Jan 22 21:23:57 2019
New Revision: 268163

URL: https://gcc.gnu.org/viewcvs?rev=268163&root=gcc&view=rev
Log:
2019-01-22  Harald Anlauf  <anlauf@gmx.de>

        PR fortran/88579
        * trans-expr.c (gfc_conv_power_op): Handle cases of (2**e) ** integer
        and (- 2**e) ** integer.

2019-01-22  Harald Anlauf  <anlauf@gmx.de>

        PR fortran/88579
        * gfortran.dg/power_8.f90: New test.


Added:
    trunk/gcc/testsuite/gfortran.dg/power_8.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 21:49:09 2019
Return-Path: <gcc-bugs-return-630367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78382 invoked by alias); 22 Jan 2019 21:49:08 -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 78085 invoked by uid 48); 22 Jan 2019 21:49:03 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88995] New: [8/9 Regression] internal compiler error: in lookup_template_class_1, at cp/pt.c:9471
Date: Tue, 22 Jan 2019 21:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88995-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: 2019-01/txt/msg03176.txt.bz2
Content-length: 3423

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

            Bug ID: 88995
           Summary: [8/9 Regression] internal compiler error: in
                    lookup_template_class_1, at cp/pt.c:9471
           Product: gcc
           Version: 8.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: nathan at gcc dot gnu.org
  Target Milestone: ---

On gcc-8-branch, r268029 caused

/builddir/build/BUILD/dldt-2018_R3/inference-engine/thirdparty/mkl-dnn/src/cpu/simple_reorder.hpp:1393:67:
internal compiler error: in lookup_template_class_1, at cp/pt.c:9471
0xad14be lookup_template_class_1
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:9471
0xad2db0 lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*,
int, int)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:9683
0xadf026 tsubst_aggr_type
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:12686
0xaee57b tsubst_copy
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:15462
0xb0308c tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:19060
0xafce36 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:17756
0xae73dc tsubst_decl
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:13779
0xaee8a2 tsubst_copy
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:15507
0xb0423b tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:19259
0xafe978 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:18169
0xaff5d9 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:18348
0xaff9f8 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:18381
0xaff633 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:18349
0xaff5d9 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:18348
0xafce36 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:17756
0xaeddf0 tsubst_init
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:15350
0xaf7052 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:16997
0xaf5eca tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:16862
0xaf7366 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:17027
0xaf5eca tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        /export/gnu/import/git/sources/gcc/gcc/cp/pt.c:16862
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

I am working on a smaller testcase.
>From gcc-bugs-return-630368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:03:44 2019
Return-Path: <gcc-bugs-return-630368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98319 invoked by alias); 22 Jan 2019 22:03:44 -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 97732 invoked by uid 48); 22 Jan 2019 22:03:39 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] New: Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Tue, 22 Jan 2019 22:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88996-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: 2019-01/txt/msg03177.txt.bz2
Content-length: 580

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

            Bug ID: 88996
           Summary: Implement P0439R0 - Make std::memory_order a scoped
                    enumeration.
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: emsr at gcc dot gnu.org
  Target Milestone: ---

Basically make memory_order an enum class and make constexpr aliases to teh old
names.
Without breaking ABI.
>From gcc-bugs-return-630369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:07:08 2019
Return-Path: <gcc-bugs-return-630369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104077 invoked by alias); 22 Jan 2019 22:07:06 -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 104042 invoked by uid 48); 22 Jan 2019 22:07:02 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88981] [nvptx, openacc, libgomp] How to handle async regions without corresponding wait
Date: Tue, 22 Jan 2019 22:07: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88981-4-VbRs5kKhWk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88981-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: 2019-01/txt/msg03178.txt.bz2
Content-length: 228

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Thomas,

any comments to add from OpenACC perspective? What is correct or desirable
behaviour?

Thanks,
- Tom
>From gcc-bugs-return-630370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:12:45 2019
Return-Path: <gcc-bugs-return-630370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111069 invoked by alias); 22 Jan 2019 22:12:44 -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 111000 invoked by uid 48); 22 Jan 2019 22:12:40 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Tue, 22 Jan 2019 22:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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 attachments.created
Message-ID: <bug-88996-4-valmyzsrsV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88996-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: 2019-01/txt/msg03179.txt.bz2
Content-length: 1285

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

emsr at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emsr at gcc dot gnu.org

--- Comment #1 from emsr at gcc dot gnu.org ---
Created attachment 45499
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45499&action=edit
Patch that just does the thing for C++11 onwards.

I did

ed@bad-horse:~/bin$ nm  lib64/libstdc++.so | grep memory_order
00000000000a9120 T _ZNSt9__atomic011atomic_flag12test_and_setESt12memory_order
00000000000a9170 T _ZNSt9__atomic011atomic_flag5clearESt12memory_order
00000000000a9120 T
_ZNVSt9__atomic011atomic_flag12test_and_setESt12memory_order@@GLIBCXX_3.4.11

and

ed@bad-horse:~/bin$ nm  lib32/libstdc++.so | grep memory_order
0008ae00 T _ZNSt9__atomic011atomic_flag12test_and_setESt12memory_order
0008ae70 T _ZNSt9__atomic011atomic_flag5clearESt12memory_order
0008ae00 T
_ZNVSt9__atomic011atomic_flag12test_and_setESt12memory_order@@GLIBCXX_3.4.11
0008ae70 T _ZNVSt9__atomic011atomic_flag5clearESt12memory_order@@GLIBCXX_3.4.11

on x96_64-linux.

This is what all teh abi files have.
We'll need to check this on all the targets.
>From gcc-bugs-return-630371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:13:08 2019
Return-Path: <gcc-bugs-return-630371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111978 invoked by alias); 22 Jan 2019 22:13:07 -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 111919 invoked by uid 48); 22 Jan 2019 22:13:03 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Tue, 22 Jan 2019 22:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88996-4-zgQTpY0p6U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88996-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: 2019-01/txt/msg03180.txt.bz2
Content-length: 121

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

--- Comment #2 from emsr at gcc dot gnu.org ---
Still testing BTW.
>From gcc-bugs-return-630372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:18:21 2019
Return-Path: <gcc-bugs-return-630372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 877 invoked by alias); 22 Jan 2019 22:18: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 832 invoked by uid 48); 22 Jan 2019 22:18:16 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88995] [8/9 Regression] internal compiler error: in lookup_template_class_1, at cp/pt.c:9471
Date: Tue, 22 Jan 2019 22:18: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone
Message-ID: <bug-88995-4-6ixn5vKMbr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88995-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: 2019-01/txt/msg03181.txt.bz2
Content-length: 341

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |8.2.0
   Target Milestone|---                         |8.3
>From gcc-bugs-return-630373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:28:16 2019
Return-Path: <gcc-bugs-return-630373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24191 invoked by alias); 22 Jan 2019 22:28:15 -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 24059 invoked by uid 55); 22 Jan 2019 22:28:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87064] [9 regression] libgomp.oacc-fortran/reduction-3.f90 fails starting with r263751
Date: Tue, 22 Jan 2019 22:28: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: 9.0
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wschmidt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87064-4-cKMc1HlFHR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87064-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: 2019-01/txt/msg03182.txt.bz2
Content-length: 463

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

--- Comment #24 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 22:27:32 2019
New Revision: 268164

URL: https://gcc.gnu.org/viewcvs?rev=268164&root=gcc&view=rev
Log:
        PR target/87064
        * config/rs6000/vsx.md (*vsx_reduc_<VEC_reduc_name>_v2df_scalar):
        Disable for little endian.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/rs6000/vsx.md
>From gcc-bugs-return-630374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:29:19 2019
Return-Path: <gcc-bugs-return-630374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25723 invoked by alias); 22 Jan 2019 22:29:18 -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 25615 invoked by uid 55); 22 Jan 2019 22:29:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88968] [8/9 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 22:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88968-4-bdREIhJj3r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg03183.txt.bz2
Content-length: 804

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 22:28:42 2019
New Revision: 268165

URL: https://gcc.gnu.org/viewcvs?rev=268165&root=gcc&view=rev
Log:
        PR middle-end/88968
        * gimplify.c (gimplify_omp_atomic): Handle bitfield atomics with
        non-integral DECL_BIT_FIELD_REPRESENTATIVEs.

        * c-omp.c (c_finish_omp_atomic): For bitfield atomics, update type
        variable after using BIT_FIELD_REF.

        * c-c++-common/gomp/atomic-23.c: New test.

Added:
    trunk/gcc/testsuite/c-c++-common/gomp/atomic-23.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/c-family/ChangeLog
    trunk/gcc/c-family/c-omp.c
    trunk/gcc/gimplify.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:31:33 2019
Return-Path: <gcc-bugs-return-630375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30489 invoked by alias); 22 Jan 2019 22:31:32 -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 30408 invoked by uid 55); 22 Jan 2019 22:31:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 22:31: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88965-4-cw7LlPmSIw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg03184.txt.bz2
Content-length: 721

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 22 22:30:44 2019
New Revision: 268166

URL: https://gcc.gnu.org/viewcvs?rev=268166&root=gcc&view=rev
Log:
        PR target/88965
        * config/rs6000/rs6000.c: Include tree-vrp.h and tree-ssanames.h.
        (rs6000_gimple_fold_builtin): If MEM_REF address doesn't satisfy
        is_gimple_mem_ref_addr predicate, force it into a SSA_NAME first.

        * gcc.target/powerpc/pr88965.c: New test.

Added:
    trunk/gcc/testsuite/gcc.target/powerpc/pr88965.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/rs6000/rs6000.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:37:25 2019
Return-Path: <gcc-bugs-return-630376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47718 invoked by alias); 22 Jan 2019 22:37:25 -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 43708 invoked by uid 48); 22 Jan 2019 22:37:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88965] powerpc64le vector builtin hits ICE in verify_gimple
Date: Tue, 22 Jan 2019 22:37: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88965-4-yLWPxTIuM8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88965-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: 2019-01/txt/msg03185.txt.bz2
Content-length: 146

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-630377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:37:37 2019
Return-Path: <gcc-bugs-return-630377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56430 invoked by alias); 22 Jan 2019 22:37:36 -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 52885 invoked by uid 48); 22 Jan 2019 22:37:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88968] [8 Regression] Stack overflow in gimplify_expr
Date: Tue, 22 Jan 2019 22:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88968-4-P7kV2HBGfO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88968-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: 2019-01/txt/msg03186.txt.bz2
Content-length: 475

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[8/9 Regression] Stack      |[8 Regression] Stack
                   |overflow in gimplify_expr   |overflow in gimplify_expr

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-630378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:41:05 2019
Return-Path: <gcc-bugs-return-630378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14646 invoked by alias); 22 Jan 2019 22:41:05 -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 14614 invoked by uid 48); 22 Jan 2019 22:41:01 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88989] ICE in resolvePropertiesX, at d/dmd/expression.c:251
Date: Tue, 22 Jan 2019 22:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88989-4-99v3VudSSV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88989-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88989-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: 2019-01/txt/msg03187.txt.bz2
Content-length: 275

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

--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
I thought that the test case looked familiar.

https://issues.dlang.org/show_bug.cgi?id=18057

I had fixed this before in the D implementation branch.
>From gcc-bugs-return-630379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 22:44:49 2019
Return-Path: <gcc-bugs-return-630379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20174 invoked by alias); 22 Jan 2019 22:44:48 -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 20077 invoked by uid 48); 22 Jan 2019 22:44:43 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators
Date: Tue, 22 Jan 2019 22:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wojciech_mula at poczta dot onet.pl
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:
Message-ID: <bug-88916-4-7yH8Hnc6P6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88916-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: 2019-01/txt/msg03188.txt.bz2
Content-length: 826

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

--- Comment #3 from Wojciech Mula <wojciech_mula at poczta dot onet.pl> ---
A similar case:

---sign.c---
int different_sign(long a, long b) {
    return (a >= 0 && b < 0) || (a < 0 && b >= 0);
}
---eof--

This is compiled into:

different_sign:
        notq    %rdi
        movq    %rdi, %rax
        notq    %rsi
        shrq    $63, %rax
        shrq    $63, %rsi
        xorl    %esi, %eax
        movzbl  %al, %eax
        ret

When expressed as difference of the sign bits

    ((unsigned long)a ^ (unsigned long)b) >> 63

the code is way shorter:

different_sign:
    xorq        %rsi, %rdi
    movq        %rdi, %rax
    shrq        $63, %rax

BTW, I looked at ARM assembly, and GCC also emits
two shifts, so the observed behaviour is not limited
by a target.
>From gcc-bugs-return-630380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:18:19 2019
Return-Path: <gcc-bugs-return-630380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17620 invoked by alias); 22 Jan 2019 23:18:18 -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 17531 invoked by uid 48); 22 Jan 2019 23:18:14 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88993] GCC 9 -Wformat-overflow=2 should reflect real libc limits
Date: Tue, 22 Jan 2019 23:18: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords
Message-ID: <bug-88993-4-blEtNLSHro@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88993-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: 2019-01/txt/msg03189.txt.bz2
Content-length: 2587

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic

--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Quoting my response in a private discussion:

The warning was prompted by a limitation in Glibc(*) where its sprintf would
fail for some directives that produced more output than 4k.  I don't know if
any other implementations have similar limitations and the warning doesn't try
to adjust to specific implementations.

The warning is handled by a pass that both detects possible bugs and optimizes
calls to formatted I/O functions.  GCC needs to avoid optimizing results of
calls to these functions on the assumption that the library calls succeed under
these conditions.  So the warning is both a reminder that the code may be
unportable (i.e., it could fail and result in unexpected truncation of output)
and less efficient.  This is more relevant to the string I/O functions like
sprintf than to file I/O where output truncation may happen under all sorts of
conditions, and that GCC doesn't for the most part attempt to optimize.

At the same time, level 2 of the -Wformat-overflow warning is designed to be
strict even at the cost of some false positives.  When the warning doesn't know
whether a call is safe, at level 2 it errs on the side of caution and triggers.
 There are many other cases when the warning is issued even for safe code, so
this one doesn't seem any worse to me.  But if it is causing hardship (e.g.,
too many instances) we might want to think about adjusting it somehow.  (For
instance, we could limit the warning to the string formatting functions and
avoid issuing it for printf/fprintf; or we could only issue it when -Wpedantic
is also specified; or we could add a new warning, say -Wportability, for these
kinds of problems.)

The Glibc limitation/bug still exists in current versions:

  https://bugzilla.redhat.com/show_bug.cgi?id=441945
  https://sourceware.org/bugzilla/show_bug.cgi?id=21127

It affects directives that produce lots of output, usually because of very
large width or precision.  In very simple tests the threshold where it starts
to dynamically allocate memory is around 64k, like in this call:

  snprintf (0, 0, "%.65505i", 1);

or this one:

  snprintf (0, 0, "%65505s", "");

Depending on when malloc fails, either the call fails or crashes.
>From gcc-bugs-return-630381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:19:58 2019
Return-Path: <gcc-bugs-return-630381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86681 invoked by alias); 22 Jan 2019 23:19:57 -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 71052 invoked by uid 48); 22 Jan 2019 23:19:51 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Tue, 22 Jan 2019 23:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88996-4-oyHTPHmidd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88996-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: 2019-01/txt/msg03190.txt.bz2
Content-length: 807

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-22
     Ever confirmed|0                           |1

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The ABI says the mangling is the same for scoped and unscoped enumeration
types. There are some corner cases with decltype expressions in function
template declarations, where the enumerator names show up, but I don't expect
them to happen in real code.

I'm not sure if we want to do this for older standards though, it wasn't a DR.
>From gcc-bugs-return-630382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:20:58 2019
Return-Path: <gcc-bugs-return-630382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107314 invoked by alias); 22 Jan 2019 23:20:57 -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 100927 invoked by uid 48); 22 Jan 2019 23:20:53 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88997] New: Implicit constructors created with line numbers
Date: Tue, 22 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88997-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: 2019-01/txt/msg03191.txt.bz2
Content-length: 4754

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

            Bug ID: 88997
           Summary: Implicit constructors created with line numbers
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jg at jguk dot org
  Target Milestone: ---

Created attachment 45500
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45500&action=edit
test case

Hello

Could the implicit copy constructor be created with line numbers? Maybe also
source code saved as a temp file?

Or alternatively the struct could be used (example output below)

Test case attached. It is clearer to know which variable the runtime error
relates

e.g. expected output something like:

$ ./undef
undef.cpp:9:10: runtime error: load of value 112, which is not a valid value
for type 'bool'
undef.cpp:10:10: runtime error: load of value 102, which is not a valid value
for type 'bool'
undef.cpp:11:10: runtime error: load of value 172, which is not a valid value
for type 'bool'



Actual output:

$ export UBSAN_OPTIONS=print_stacktrace=1

$ ./undef
undef.cpp:6:16: runtime error: load of value 112, which is not a valid value
for type 'bool'
    #0 0x55e6f8f5fa63 in testt::testt(testt const&)
/home/jonny/code/sanitize_undefined/undef.cpp:6
    #1 0x55e6f8f5fd85 in void __gnu_cxx::new_allocator<testt>::construct<testt,
testt const&>(testt*, testt const&) /usr/include/c++/8/ext/new_allocator.h:136
    #2 0x55e6f8f5e911 in void std::allocator_traits<std::allocator<testt>
>::construct<testt, testt const&>(std::allocator<testt>&, testt*, testt const&)
/usr/include/c++/8/bits/alloc_traits.h:475
    #3 0x55e6f8f5eecc in void std::vector<testt, std::allocator<testt>
>::_M_realloc_insert<testt const&>(__gnu_cxx::__normal_iterator<testt*,
std::vector<testt, std::allocator<testt> > >, testt const&)
/usr/include/c++/8/bits/vector.tcc:436
    #4 0x55e6f8f5e551 in std::vector<testt, std::allocator<testt>
>::push_back(testt const&) /usr/include/c++/8/bits/stl_vector.h:1085
    #5 0x55e6f8f5dd97 in main /home/jonny/code/sanitize_undefined/undef.cpp:18
    #6 0x7fcbbf157b96 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
    #7 0x55e6f8f5dc09 in _start
(/home/jonny/code/sanitize_undefined/undef+0x7c09)

undef.cpp:6:16: runtime error: load of value 76, which is not a valid value for
type 'bool'
    #0 0x55e6f8f5fb61 in testt::testt(testt const&)
/home/jonny/code/sanitize_undefined/undef.cpp:6
    #1 0x55e6f8f5fd85 in void __gnu_cxx::new_allocator<testt>::construct<testt,
testt const&>(testt*, testt const&) /usr/include/c++/8/ext/new_allocator.h:136
    #2 0x55e6f8f5e911 in void std::allocator_traits<std::allocator<testt>
>::construct<testt, testt const&>(std::allocator<testt>&, testt*, testt const&)
/usr/include/c++/8/bits/alloc_traits.h:475
    #3 0x55e6f8f5eecc in void std::vector<testt, std::allocator<testt>
>::_M_realloc_insert<testt const&>(__gnu_cxx::__normal_iterator<testt*,
std::vector<testt, std::allocator<testt> > >, testt const&)
/usr/include/c++/8/bits/vector.tcc:436
    #4 0x55e6f8f5e551 in std::vector<testt, std::allocator<testt>
>::push_back(testt const&) /usr/include/c++/8/bits/stl_vector.h:1085
    #5 0x55e6f8f5dd97 in main /home/jonny/code/sanitize_undefined/undef.cpp:18
    #6 0x7fcbbf157b96 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
    #7 0x55e6f8f5dc09 in _start
(/home/jonny/code/sanitize_undefined/undef+0x7c09)

undef.cpp:6:16: runtime error: load of value 22, which is not a valid value for
type 'bool'
    #0 0x55e6f8f5fc64 in testt::testt(testt const&)
/home/jonny/code/sanitize_undefined/undef.cpp:6
    #1 0x55e6f8f5fd85 in void __gnu_cxx::new_allocator<testt>::construct<testt,
testt const&>(testt*, testt const&) /usr/include/c++/8/ext/new_allocator.h:136
    #2 0x55e6f8f5e911 in void std::allocator_traits<std::allocator<testt>
>::construct<testt, testt const&>(std::allocator<testt>&, testt*, testt const&)
/usr/include/c++/8/bits/alloc_traits.h:475
    #3 0x55e6f8f5eecc in void std::vector<testt, std::allocator<testt>
>::_M_realloc_insert<testt const&>(__gnu_cxx::__normal_iterator<testt*,
std::vector<testt, std::allocator<testt> > >, testt const&)
/usr/include/c++/8/bits/vector.tcc:436
    #4 0x55e6f8f5e551 in std::vector<testt, std::allocator<testt>
>::push_back(testt const&) /usr/include/c++/8/bits/stl_vector.h:1085
    #5 0x55e6f8f5dd97 in main /home/jonny/code/sanitize_undefined/undef.cpp:18
    #6 0x7fcbbf157b96 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21b96)
    #7 0x55e6f8f5dc09 in _start
(/home/jonny/code/sanitize_undefined/undef+0x7c09)
>From gcc-bugs-return-630383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:23:38 2019
Return-Path: <gcc-bugs-return-630383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124050 invoked by alias); 22 Jan 2019 23:23:37 -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 124023 invoked by uid 48); 22 Jan 2019 23:23:34 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Tue, 22 Jan 2019 23:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi 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:
Message-ID: <bug-88996-4-rkgM36PfZD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88996-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: 2019-01/txt/msg03192.txt.bz2
Content-length: 850

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
+  inline constexpr memory_order
+  operator&(memory_order __m1, memory_order __m2)
+  { return memory_order(int(__m1) & int(__m2)); }
+
+  inline constexpr memory_order
+  operator|(memory_order __m1, memory_order __m2)
+  { return memory_order(int(__m1) | int(__m2)); }

What are these operators for? One of the main points of P0439 was that this
isn't a bitmask type, and combining the values doesn't make sense. Quoting the
paper:

> a scoped enumeration is more strongly typed, disallowing implicit
> conversion to integers, and preventing nonsensical expressions such as
> memory_order_acquire|memory_order_release (which could be mistakenly
> assumed to be equivalent to memory_order_acq_rel) or ~memory_order_relaxed.
>From gcc-bugs-return-630384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:36:40 2019
Return-Path: <gcc-bugs-return-630384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15797 invoked by alias); 22 Jan 2019 23:36: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 15755 invoked by uid 48); 22 Jan 2019 23:36:34 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88998] New: bad codegen with mmx instructions for unordered_map
Date: Tue, 22 Jan 2019 23:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88998-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: 2019-01/txt/msg03193.txt.bz2
Content-length: 1519

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

            Bug ID: 88998
           Summary: bad codegen with mmx instructions for unordered_map
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: barry.revzin at gmail dot com
  Target Milestone: ---

This program should be valid:

#include <cassert>
#include <unordered_map>
#include <x86intrin.h>

[[gnu::noinline]]
double prepare(int a, int b)
{
    __m128i is = _mm_setr_epi32(a, b, 0, 0);
    __m128d ds =_mm_cvtepi32_pd(is);
    return ds[0] + ds[1];
}

int main(int, char**) {
    double d = prepare(1, 2);

    std::unordered_map<int, int> m;
    m.insert({0, 0});
    m.insert({1, 1});
    assert(m.load_factor() <= m.max_load_factor());

    return d;
}


But if I use MMX instructions, the assertion triggers:

$ g++ -std=c++11 -march=haswell -mtune=haswell -mavx -O3 foo.cxx && ./a.out
a.out: foo.cxx:19: int main(int, char**): Assertion `m.load_factor() <=
m.max_load_factor()' failed.
Aborted (core dumped)

Whereas it does not if I explicitly remove them:

$ g++ -std=c++11 -march=haswell -mtune=haswell -mavx -mno-mmx -O3 foo.cxx &&
./a.out
$ 

Additionally, adding a call to _mm_empty() right before the return statement in
prepare() fixes the issue. 

If you look at the load_factor(), it returns 2 (and then 3 on the next insert,
etc.)
>From gcc-bugs-return-630385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:39:11 2019
Return-Path: <gcc-bugs-return-630385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112975 invoked by alias); 22 Jan 2019 23:39:11 -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 108318 invoked by uid 48); 22 Jan 2019 23:39:07 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88999] New: [9 Regression] testcases using in_avail() fail on nios2-elf
Date: Tue, 22 Jan 2019 23:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88999-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: 2019-01/txt/msg03194.txt.bz2
Content-length: 1552

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

            Bug ID: 88999
           Summary: [9 Regression] testcases using in_avail() fail on
                    nios2-elf
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sandra at gcc dot gnu.org
  Target Milestone: ---

I'm seeing some libstdc++ test regressions on nios2-elf testing on mainline. 
The symptoms are assertion failures about the results of calls to in_avail().

# Assertion 'strmsz_1 > strmsz_2' failed.
FAIL: 27_io/basic_filebuf/sgetn/char/1-in.cc execution test
FAIL: 27_io/basic_filebuf/sgetn/char/1-io.cc execution test
FAIL: 27_io/basic_filebuf/sgetn/char/2-in.cc execution test
FAIL: 27_io/basic_filebuf/sgetn/char/2-io.cc execution test

# Assertion 'i != 0' failed.
FAIL: 27_io/basic_istream/readsome/char/6746-2.cc execution test
FAIL: 27_io/basic_istream/readsome/wchar_t/6746-2.cc execution test

I see that these tests are xfailed for bare-metal ARM targets with a note that
ARM semihosting doesn't support the underlying fstat call, but that is not true
of nios2.  These tests all passed on nios2-elf with GCC 8.

I realize it is hard for other people to test this target, but I'd be happy to
test a patch or do some debugging to try to track it down given some clues
about where to look.  (Maybe this failure rings a bell with someone already
familiar with the code?)
>From gcc-bugs-return-630386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:43:09 2019
Return-Path: <gcc-bugs-return-630386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124158 invoked by alias); 22 Jan 2019 23:43:07 -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 124079 invoked by uid 48); 22 Jan 2019 23:43:04 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 22 Jan 2019 23:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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: attachments.created
Message-ID: <bug-88713-4-RvUAYYjTym@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03195.txt.bz2
Content-length: 1940

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

--- Comment #28 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45501
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45501&action=edit
Minimum working example of the rsqrt problem. Can be compiled with: gcc -Ofast
-S -march=skylake-avx512 -mprefer-vector-width=512 -shared -fPIC rsqrt.c -o
rsqrt.s

I attached a minimum working example, demonstrating the problem of excessive
code generation for reciprocal square root, in the file rsqrt.c.
You can compile with:

gcc -Ofast -S -march=skylake-avx512 -mprefer-vector-width=512 -shared -fPIC
rsqrt.c -o rsqrt.s

clang -Ofast -S -march=skylake-avx512 -mprefer-vector-width=512 -shared -fPIC
rsqrt.c -o rsqrt.s

Or compare the asm of both on Godbolt: https://godbolt.org/z/c7Z0En

For gcc:

        vmovups (%rsi), %zmm0
        vxorps  %xmm1, %xmm1, %xmm1
        vcmpps  $4, %zmm0, %zmm1, %k1
        vrsqrt14ps      %zmm0, %zmm1{%k1}{z}
        vmulps  %zmm0, %zmm1, %zmm2
        vmulps  %zmm1, %zmm2, %zmm0
        vmulps  .LC1(%rip), %zmm2, %zmm2
        vaddps  .LC0(%rip), %zmm0, %zmm0
        vmulps  %zmm2, %zmm0, %zmm0
        vrcp14ps        %zmm0, %zmm1
        vmulps  %zmm0, %zmm1, %zmm0
        vmulps  %zmm0, %zmm1, %zmm0
        vaddps  %zmm1, %zmm1, %zmm1
        vsubps  %zmm0, %zmm1, %zmm0
        vmovups %zmm0, (%rdi)

for Clang:

        vmovups (%rsi), %zmm0
        vrsqrt14ps      %zmm0, %zmm1
        vmulps  %zmm1, %zmm0, %zmm0
        vfmadd213ps     .LCPI0_0(%rip){1to16}, %zmm1, %zmm0 # zmm0 = (zmm1 *
zmm0) + mem
        vmulps  .LCPI0_1(%rip){1to16}, %zmm1, %zmm1
        vmulps  %zmm0, %zmm1, %zmm0
        vmovups %zmm0, (%rdi)

Clang looks like it is is doing
 /*     rsqrt(a) = -0.5     * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0)
*/

where .LCPI0_0(%rip) = -3.0 and LCPI0_1(%rip) = -0.5.
gcc is doing much more, and fairly different.
>From gcc-bugs-return-630387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 22 23:47:14 2019
Return-Path: <gcc-bugs-return-630387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30427 invoked by alias); 22 Jan 2019 23:47:13 -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 29620 invoked by uid 48); 22 Jan 2019 23:47:08 -0000
From: "steven.w.carmer at lmco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/89000] New: gcov --function-summaries says No branches/No calls, only the File summary is correct
Date: Tue, 22 Jan 2019 23:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steven.w.carmer at lmco dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-89000-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: 2019-01/txt/msg03196.txt.bz2
Content-length: 2869

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

            Bug ID: 89000
           Summary: gcov --function-summaries says No branches/No calls,
                    only the File summary is correct
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: steven.w.carmer at lmco dot com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

gcc -v output
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/appl/lucy_local_sde/Linux-RHEL7-x86_64/gcc-8.2.0/bin/../libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/appl/lucy_local_sde/src/gcc/gcc-8.2.0/x86_64-Linux-3.10/gcc-8.2.0-obj/../gcc-8.2.0/configure
--prefix=/usr/local/sde/gcc-8.2.0 --disable-nls --enable-shared --enable-static
--enable-multilib --with-multilib-list=m32,m64 --enable-languages=c,c++,fortran
Thread model: posix
gcc version 8.2.0 (GCC) 

When using the -f (--function-summaries) option with gcov, it does not provide
the branch/call statistics for the functions. The file summary is correct, and
the *gcov output file that gets created shows it has the branch/call
information that the -f option relies upon, but the gcov -f output just shows
"No branches/No calls" for all the function summaries.

A trivial example source code file gcov_test.c that produces these results:

#include <stdio.h>
#include <stdlib.h>
#include <stdbool.h>

void foo(void);
void foo(void)
{
  static bool firstPass = true;

  if (firstPass)
  {
    firstPass = false;
    printf ("First Pass\n");
  }
  else
  {
    printf ("Not First Pass\n");
  }
}

int main (int argc, char *argv[])
{

  foo();
  foo();
  foo();

  return 0;
}

Compile that C file with the following:
gcc -fprofile-arcs -ftest-coverage gcov_test.c

Run the executable to produce the gcov artifacts
./a.out

And then run the following to view the coverage report
gcov -b gcov_test.c -f

Function 'main'
Lines executed:100.00% of 5
No branches
No calls

Function 'foo'
Lines executed:100.00% of 6
No branches
No calls

File 'gcov_test.c'
Lines executed:100.00% of 11
Branches executed:100.00% of 2
Taken at least once:100.00% of 2
Calls executed:100.00% of 5
Creating 'gcov_test.c.gcov'

Note the "No branches" and "No calls" output. With gcc/gcov 7.4 (and older),
the output looks like this:

Function 'main'
Lines executed:100.00% of 5
No branches
Calls executed:100.00% of 3

Function 'foo'
Lines executed:100.00% of 6
Branches executed:100.00% of 2
Taken at least once:100.00% of 2
Calls executed:100.00% of 2

File 'gcov_test.c'
Lines executed:100.00% of 11
Branches executed:100.00% of 2
Taken at least once:100.00% of 2
Calls executed:100.00% of 5
Creating 'gcov_test.c.gcov'
>From gcc-bugs-return-630388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 00:11:09 2019
Return-Path: <gcc-bugs-return-630388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114223 invoked by alias); 23 Jan 2019 00:11:08 -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 114071 invoked by uid 48); 23 Jan 2019 00:11:00 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Wed, 23 Jan 2019 00:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr 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:
Message-ID: <bug-88996-4-7QgDFSayqp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88996-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: 2019-01/txt/msg03197.txt.bz2
Content-length: 1167

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

--- Comment #5 from emsr at gcc dot gnu.org ---
I was a bit surprised I "needed" these. There are apparently some uses of
these.
I'll roll back and show you...

/home/ed/obj/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/atomic_base.h:104:7:
error: no match for â€˜operator|â€™ (operand types are â€˜std::memory_orderâ€™ and
â€˜std::memory_orderâ€™)
  103 |     return memory_order(__cmpexch_failure_order2(__m &
__memory_order_mask)
      |                        
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                 |
      |                                                 std::memory_order
  104 |       | (__m & __memory_order_modifier_mask));
      |       ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |              |
      |              std::memory_order

Ok, I'm casting:
      | __memory_order_modifier(__m & __memory_order_modifier_mask));

This will work without the operators.
Those are sequatial flags.
Killed the ops, fix some more sadness and retest.
>From gcc-bugs-return-630389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 00:16:04 2019
Return-Path: <gcc-bugs-return-630389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119195 invoked by alias); 23 Jan 2019 00:16:03 -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 118944 invoked by uid 48); 23 Jan 2019 00:15:53 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88996] Implement P0439R0 - Make std::memory_order a scoped enumeration.
Date: Wed, 23 Jan 2019 00:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr 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: attachments.created
Message-ID: <bug-88996-4-kIIQM87M7k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88996-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: 2019-01/txt/msg03198.txt.bz2
Content-length: 273

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

--- Comment #6 from emsr at gcc dot gnu.org ---
Created attachment 45502
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45502&action=edit
New patch, C++20 only, several fixes, no memory_order ops.

Retesting.
>From gcc-bugs-return-630390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 01:01:16 2019
Return-Path: <gcc-bugs-return-630390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47817 invoked by alias); 23 Jan 2019 01:01:16 -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 47710 invoked by uid 48); 23 Jan 2019 01:01:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88985] [9 Regression] ICE in estimate_edge_devirt_benefit, at ipa-fnsummary.c:2585
Date: Wed, 23 Jan 2019 01:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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: bug_status cf_reconfirmed_on cc cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-88985-4-Yf2l74zg30@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88985-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: 2019-01/txt/msg03199.txt.bz2
Content-length: 1018

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
                 CC|                            |msebor at gcc dot gnu.org
      Known to work|                            |8.2.0
     Ever confirmed|0                           |1
      Known to fail|                            |9.0

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed.  Bisection points to r261744:

r261744 | marxin | 2018-06-19 10:31:20 -0400 (Tue, 19 Jun 2018) | 75 lines

Clean-up usage of ipa_fn_summary and ipa_call_summary summaries.

The result of the following call is null, and so the dereference in the return
statement below crashes:

  isummary = ipa_fn_summaries->get (callee);
  return isummary->inlinable;
>From gcc-bugs-return-630391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 01:03:00 2019
Return-Path: <gcc-bugs-return-630391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50445 invoked by alias); 23 Jan 2019 01:02:59 -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 50303 invoked by uid 48); 23 Jan 2019 01:02:55 -0000
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89001] New: g++ uses wrong mangling for lifetime-extended temporaries
Date: Wed, 23 Jan 2019 01:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: richard-gccbugzilla at metafoo dot co.uk
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89001-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: 2019-01/txt/msg03200.txt.bz2
Content-length: 773

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

            Bug ID: 89001
           Summary: g++ uses wrong mangling for lifetime-extended
                    temporaries
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: richard-gccbugzilla at metafoo dot co.uk
  Target Milestone: ---

Consider:

inline int &&r = 0;
int *p = &r;

GCC mangles the lifetime-extended temporary as _ZGR1r0, which doesn't match the
ABI mangling rule
(http://itanium-cxx-abi.github.io/cxx-abi/abi.html#mangling-special-temporaries).
The mangling required by the ABI (and produced by Clang) is _ZGR1r_
>From gcc-bugs-return-630392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 01:50:38 2019
Return-Path: <gcc-bugs-return-630392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26979 invoked by alias); 23 Jan 2019 01:50:37 -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 25787 invoked by uid 48); 23 Jan 2019 01:50:33 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88987] [9 Regression] ICE: unexpected expression '(bool)sm' of kind implicit_conv_expr
Date: Wed, 23 Jan 2019 01:50: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-88987-4-dgLOWnBk2q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88987-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88987-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: 2019-01/txt/msg03201.txt.bz2
Content-length: 614

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
                 CC|                            |mpolacek at gcc dot gnu.org
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-630393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 01:52:05 2019
Return-Path: <gcc-bugs-return-630393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50636 invoked by alias); 23 Jan 2019 01:52:05 -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 49751 invoked by uid 48); 23 Jan 2019 01:52:01 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88987] [9 Regression] ICE: unexpected expression '(bool)sm' of kind implicit_conv_expr
Date: Wed, 23 Jan 2019 01:52: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88987-4-kyXl71YRHN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88987-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88987-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: 2019-01/txt/msg03202.txt.bz2
Content-length: 144

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

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r266874.
>From gcc-bugs-return-630394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 02:08:06 2019
Return-Path: <gcc-bugs-return-630394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66901 invoked by alias); 23 Jan 2019 02:08:05 -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 66631 invoked by uid 48); 23 Jan 2019 02:08:01 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88986] [7/8/9 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in member_vec_binary_search, at cp/name-lookup.c:1136
Date: Wed, 23 Jan 2019 02:08: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88986-4-aOdgRm0ly0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88986-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88986-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: 2019-01/txt/msg03203.txt.bz2
Content-length: 1188

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
                 CC|                            |mpolacek at gcc dot gnu.org
   Target Milestone|---                         |7.5
            Summary|[9 Regression] ICE: tree    |[7/8/9 Regression] ICE:
                   |check: expected tree that   |tree check: expected tree
                   |contains 'decl minimal'     |that contains 'decl
                   |structure, have             |minimal' structure, have
                   |'error_mark' in             |'error_mark' in
                   |member_vec_binary_search,   |member_vec_binary_search,
                   |at cp/name-lookup.c:1136    |at cp/name-lookup.c:1136
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-630395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 02:09:37 2019
Return-Path: <gcc-bugs-return-630395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81811 invoked by alias); 23 Jan 2019 02:09:37 -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 80880 invoked by uid 48); 23 Jan 2019 02:09:33 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88986] [7/8/9 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in member_vec_binary_search, at cp/name-lookup.c:1136
Date: Wed, 23 Jan 2019 02:09: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88986-4-kuKp79frMA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88986-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88986-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: 2019-01/txt/msg03204.txt.bz2
Content-length: 144

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

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r244246.
>From gcc-bugs-return-630397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 02:49:56 2019
Return-Path: <gcc-bugs-return-630397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130548 invoked by alias); 23 Jan 2019 02:49:52 -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 129934 invoked by uid 48); 23 Jan 2019 02:49:47 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89002] New: ICE in scan_omp_1_op, at omp-low.c:3166
Date: Wed, 23 Jan 2019 02:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89002-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: 2019-01/txt/msg03206.txt.bz2
Content-length: 6244

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

            Bug ID: 89002
           Summary: ICE in scan_omp_1_op, at omp-low.c:3166
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: openmp
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

1.

gcc-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the following
testcase w/ -fopenmp:

void
bl (int j4)
{
  int lh;
  int *u4 = &lh;

#pragma omp parallel
#pragma omp taskloop lastprivate (lh)
  for (lh = 0; lh < j4; ++lh)
    {
    }
}

% gcc-9.0.0-alpha20190120 -fopenmp -c ydeu3h7i.c
during GIMPLE pass: omplower
ydeu3h7i.c: In function 'bl':
ydeu3h7i.c:8:9: internal compiler error: in scan_omp_1_op, at omp-low.c:3166
    8 | #pragma omp taskloop lastprivate (lh)
      |         ^~~
0x6630f7 scan_omp_1_op
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:3166
0x1046ea2 walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, default_hash_traits<tree_node*> >*, tree_node*
(*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*), void*,
hash_set<tree_node*, default_hash_traits<tree_node*> >*))
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree.c:12064
0xadaa5e walk_gimple_op(gimple*, tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:221
0xadacc1 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:586
0xadae60 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:51
0xc40501 scan_omp
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:3368
0xc476f7 scan_sharing_clauses
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:1609
0xc49aca scan_omp_for
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:2337
0xc4a815 scan_omp_1_stmt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:3291
0xadac8f walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:568
0xadae60 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:51
0xadad41 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:675
0xadae60 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:51
0xc40501 scan_omp
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:3368
0xc4a5e5 scan_omp_task
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:1974
0xc4a5e5 scan_omp_1_stmt
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/omp-low.c:3280
0xadac8f walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:568
0xadae60 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:51
0xadad41 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:675
0xadae60 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/gimple-walk.c:51

2.

gcc 8.2, 7.4, 6.3 ICE differently w/ this testcase:

ydeu3h7i.c:8:9: error: non-trivial conversion at assignment
 #pragma omp taskloop lastprivate (lh)
         ^~~
<<< error >>>
int
<<< error >>> = lh;
ydeu3h7i.c:8:9: error: non-register as LHS of binary operation
<<< error >>> = <<< error >>> + 1;
ydeu3h7i.c:8: confused by earlier errors, bailing out

with -fchecking, or

during GIMPLE pass: local-fnsummary
ydeu3h7i.c: In function 'bl._omp_fn.1':
ydeu3h7i.c:12:1: internal compiler error: in estimate_operator_cost, at
tree-inline.c:3960
 }
 ^

without.

3.

Removing "#pragma omp parallel" but adding -fchecking yields PR88975 w/ gcc
9.0, 8.2, and 7.4, and aforementioned "error: non-trivial conversion at
assignment" w/ gcc 6.3.
>From gcc-bugs-return-630396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 02:49:47 2019
Return-Path: <gcc-bugs-return-630396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129843 invoked by alias); 23 Jan 2019 02:49: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 129667 invoked by uid 48); 23 Jan 2019 02:49:19 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88975] ICE: Segmentation fault (in verify_ssa or gimple_code)
Date: Wed, 23 Jan 2019 02:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88975-4-q7Fkden45r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88975-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88975-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: 2019-01/txt/msg03205.txt.bz2
Content-length: 1487

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

--- Comment #1 from Arseny Solokha <asolokha at gmx dot com> ---
--- xsihfn9u.c  2019-01-23 09:46:02.954589253 +0700
+++ msyweyyj.c  2019-01-23 09:46:13.439477032 +0700
@@ -4,7 +4,7 @@
   int ij[gy];
   int sk;

-#pragma omp taskloop reduction(+:ij)
+#pragma omp taskloop simd reduction(+:ij)
   for (sk = 0; sk < 1; ++sk)
     {
     }

% gcc-9.0.0-alpha20190120 -fopenmp -c msyweyyj.c
during GIMPLE pass: ssa
msyweyyj.c: In function 'mr._omp_fn.0':
msyweyyj.c:11:1: internal compiler error: Segmentation fault
   11 | }
      | ^
0xd701df crash_signal
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/toplev.c:326
0x98a4d8 dominated_by_p(cdi_direction, basic_block_def const*, basic_block_def
const*)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/dominance.c:1124
0xf8acd3 verify_use
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-ssa.c:872
0xf92117 verify_ssa(bool, bool)
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-ssa.c:1141
0xc89d0d execute_function_todo
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:1984
0xc8ab0e execute_todo
       
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:2031
>From gcc-bugs-return-630398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 04:38:47 2019
Return-Path: <gcc-bugs-return-630398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7012 invoked by alias); 23 Jan 2019 04:38: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 124798 invoked by uid 48); 23 Jan 2019 04:38:42 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 04:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-HBDBry0Tom@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03207.txt.bz2
Content-length: 409

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

--- Comment #29 from Marc Glisse <glisse at gcc dot gnu.org> ---
The main difference I can see is that clang computes rsqrt directly, while gcc
first computes sqrt and then computes the inverse. Also gcc seems afraid of
getting NaN for sqrt(0) so it masks out this value. ix86_emit_swsqrtsf in
gcc/config/i386/i386.c seems like a good place to look at.
>From gcc-bugs-return-630399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 04:41:59 2019
Return-Path: <gcc-bugs-return-630399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28210 invoked by alias); 23 Jan 2019 04:41:58 -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 28115 invoked by uid 48); 23 Jan 2019 04:41:54 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 04:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-5f9zqrf4KX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03208.txt.bz2
Content-length: 737

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

--- Comment #30 from Chris Elrod <elrodc at gmail dot com> ---
gcc still (In reply to Marc Glisse from comment #29)
> The main difference I can see is that clang computes rsqrt directly, while
> gcc first computes sqrt and then computes the inverse. Also gcc seems afraid
> of getting NaN for sqrt(0) so it masks out this value. ix86_emit_swsqrtsf in
> gcc/config/i386/i386.c seems like a good place to look at.

gcc caclulates the rsqrt directly with funsafe-math-optimizations and a couple
other flags (or just -ffast-math):

        vmovups (%rsi), %zmm0
        vxorps  %xmm1, %xmm1, %xmm1
        vcmpps  $4, %zmm0, %zmm1, %k1
        vrsqrt14ps      %zmm0, %zmm1{%k1}{z}
>From gcc-bugs-return-630400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 04:55:58 2019
Return-Path: <gcc-bugs-return-630400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19639 invoked by alias); 23 Jan 2019 04:55:58 -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 6890 invoked by uid 48); 23 Jan 2019 04:55:53 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 04:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-WRmYo2WOH5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03209.txt.bz2
Content-length: 586

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

--- Comment #31 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Chris Elrod from comment #30)
> gcc caclulates the rsqrt directly

No, vrsqrt14ps is just the first step in calculating sqrt here (slightly
different formula than rsqrt). vrcp14ps shows that it is computing an inverse
later. What we need to understand is why gcc doesn't try to generate rsqrt
(which would also have vrsqrt14ps, but a slightly different formula without the
comparison with 0 and masking, and without needing an inversion afterwards).
>From gcc-bugs-return-630401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 05:08:10 2019
Return-Path: <gcc-bugs-return-630401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116979 invoked by alias); 23 Jan 2019 05:08:08 -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 105275 invoked by uid 48); 23 Jan 2019 05:08:04 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88998] bad codegen with mmx instructions for unordered_map
Date: Wed, 23 Jan 2019 05:08: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88998-4-zL6GJZjgDy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88998-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: 2019-01/txt/msg03210.txt.bz2
Content-length: 799

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

Marc Glisse <glisse at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
     Ever confirmed|0                           |1

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
Indeed. Constructing {a,b,0,0} is done by constructing {a,b}, {0,0}, and
concatenating them. _mm_cvtepi32_pd starts with selecting the initial V2SI of a
V4SI. Naturally, the compiler tries to combine them, and finds sse2_cvtpi2pd to
convert directly from V2SI to V2DF. Without this simplification, everything
would have used SSE.
>From gcc-bugs-return-630402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 05:14:54 2019
Return-Path: <gcc-bugs-return-630402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112816 invoked by alias); 23 Jan 2019 05:14:53 -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 112729 invoked by uid 48); 23 Jan 2019 05:14:49 -0000
From: "wilkey at drive dot ai" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89003] New: Return inside a statement expression while initializing a static local variable fails to cleanup cxa_guard
Date: Wed, 23 Jan 2019 05:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.4.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilkey at drive dot ai
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89003-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: 2019-01/txt/msg03211.txt.bz2
Content-length: 1824

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

            Bug ID: 89003
           Summary: Return inside a statement expression while
                    initializing a static local variable fails to cleanup
                    cxa_guard
           Product: gcc
           Version: 5.4.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wilkey at drive dot ai
  Target Milestone: ---

consider the following:

void f() {
  static int i = ({
    if (true) return;
    42;
  });
}

g++ -g yields:
   0x0000000000400606 <+0>:     push   %rbp
   0x0000000000400607 <+1>:     mov    %rsp,%rbp
   0x000000000040060a <+4>:     mov    $0x601040,%eax
   0x000000000040060f <+9>:     movzbl (%rax),%eax
   0x0000000000400612 <+12>:    test   %al,%al
   0x0000000000400614 <+14>:    jne    0x40062a <f()+36>
   0x0000000000400616 <+16>:    mov    $0x601040,%edi
   0x000000000040061b <+21>:    callq  0x4004e0 <__cxa_guard_acquire@plt>
   0x0000000000400620 <+26>:    test   %eax,%eax
   0x0000000000400622 <+28>:    setne  %al
   0x0000000000400625 <+31>:    test   %al,%al
   0x0000000000400627 <+33>:    je     0x40062a <f()+36>
   0x0000000000400629 <+35>:    nop
   0x000000000040062a <+36>:    pop    %rbp
   0x000000000040062b <+37>:    retq   


Note that nothing is emitted to release the guard (neither
__cxa_guard_release() nor __cxa_guard_abort()).

The next caller of the function will either SIGABRT if on the same thread
(deadlock detection algorithm) or block forever if another thread.

Slightly more complex examples include __cxa_guard_release for cases that don't
return early, but if the early return path is taken, the emitted code will
still just JMP right over it.
>From gcc-bugs-return-630403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 05:18:55 2019
Return-Path: <gcc-bugs-return-630403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104219 invoked by alias); 23 Jan 2019 05:18:54 -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 93173 invoked by uid 48); 23 Jan 2019 05:18:50 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 05:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-UQJmBG9plG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03212.txt.bz2
Content-length: 1217

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

--- Comment #32 from Chris Elrod <elrodc at gmail dot com> ---
(In reply to Marc Glisse from comment #31)
> (In reply to Chris Elrod from comment #30)
> > gcc caclulates the rsqrt directly
> 
> No, vrsqrt14ps is just the first step in calculating sqrt here (slightly
> different formula than rsqrt). vrcp14ps shows that it is computing an
> inverse later. What we need to understand is why gcc doesn't try to generate
> rsqrt (which would also have vrsqrt14ps, but a slightly different formula
> without the comparison with 0 and masking, and without needing an inversion
> afterwards).

Okay, I think I follow you. You're saying instead of doing this (from
rguenther), which we want (also without the comparison to 0 and masking, as you
note):

 /* rsqrt(a) = -0.5     * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0) */

it is doing this, which also uses the rsqrt instruction:

 /* sqrt(a)  = -0.5 * a * rsqrtss(a) * (a * rsqrtss(a) * rsqrtss(a) - 3.0) */

and then calculating an inverse approximation of that?

The approximate sqrt, and then approximate reciprocal approximations were
slower on my computer than just vsqrt followed by div.
>From gcc-bugs-return-630404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 05:47:55 2019
Return-Path: <gcc-bugs-return-630404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113284 invoked by alias); 23 Jan 2019 05:47:54 -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 101581 invoked by uid 48); 23 Jan 2019 05:47:50 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 05:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-vvx011WVbV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03213.txt.bz2
Content-length: 759

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

--- Comment #33 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Chris Elrod from comment #32)
> (In reply to Marc Glisse from comment #31)
> > What we need to understand is why gcc doesn't try to generate rsqrt

Without -mavx512er, we do not have an expander for rsqrtv16sf2, and without
that I don't know how the machinery can guess how to use rsqrt (there are
probably ways).

> The approximate sqrt, and then approximate reciprocal approximations were
> slower on my computer than just vsqrt followed by div.

We can probably split that into the speed of sqrt vs its approximation and
inverse (div) vs its approximation. At least one of them seems to be a
pessimization on that platform.
>From gcc-bugs-return-630405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 06:53:59 2019
Return-Path: <gcc-bugs-return-630405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27453 invoked by alias); 23 Jan 2019 06:53:58 -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 20065 invoked by uid 48); 23 Jan 2019 06:53:54 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40598] Some missed optimizations in array assignment
Date: Wed, 23 Jan 2019 06:53: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.5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-40598-4-8kmYDaRa49@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-40598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-40598-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: 2019-01/txt/msg03214.txt.bz2
Content-length: 499

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

JÃ¼rgen Reuter <juergen.reuter at desy dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juergen.reuter at desy dot de

--- Comment #13 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
This seems to have been forgotten, it is still assigned. Is there any progress
on this one?
>From gcc-bugs-return-630406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:01:22 2019
Return-Path: <gcc-bugs-return-630406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57168 invoked by alias); 23 Jan 2019 07:01:09 -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 56860 invoked by uid 48); 23 Jan 2019 07:00:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88985] [9 Regression] ICE in estimate_edge_devirt_benefit, at ipa-fnsummary.c:2585
Date: Wed, 23 Jan 2019 07:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88985-4-1xX59N5HUd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88985-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: 2019-01/txt/msg03215.txt.bz2
Content-length: 471

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Then it's mine.
>From gcc-bugs-return-630407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:03:08 2019
Return-Path: <gcc-bugs-return-630407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77218 invoked by alias); 23 Jan 2019 07:03:08 -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 58854 invoked by uid 48); 23 Jan 2019 07:03:03 -0000
From: "dpzmick at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88998] bad codegen with mmx instructions for unordered_map
Date: Wed, 23 Jan 2019 07:03: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dpzmick at gmail dot com
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-88998-4-IJlP8AYllT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88998-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: 2019-01/txt/msg03216.txt.bz2
Content-length: 1180

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

David Zmick <dpzmick at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dpzmick at gmail dot com

--- Comment #2 from David Zmick <dpzmick at gmail dot com> ---
I'd like to add that we are seeing assertion fail because of the interaction
between MMX and the "long double" used in unordered_map's _M_need_rehash.

long double is forcing the use of the FPU, but the MMX instructions emitted are
wiping out the state of the FPU registers. Adding the an explicit _mm_empty (or
disabling MMX) solves the problem because it eliminates the bad interaction
with the long double in _M_need_rehash.

I'm not sure if there's a good way for developers to know when they need to add
(potentially expensive) calls to _mm_empty to vector code like this, so I feel
like I'd be less surprised if the compiler cleaned up after itself if it uses
MMX for code like this (and leave me with a performance problem to debug) than
if I ended up with the polluted FPU unexpectedly.
>From gcc-bugs-return-630408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:19:02 2019
Return-Path: <gcc-bugs-return-630408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63572 invoked by alias); 23 Jan 2019 07:19:01 -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 63458 invoked by uid 48); 23 Jan 2019 07:18:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88993] GCC 9 -Wformat-overflow=2 should reflect real libc limits
Date: Wed, 23 Jan 2019 07:19: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88993-4-3KhNAwhanV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88993-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: 2019-01/txt/msg03217.txt.bz2
Content-length: 720

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Rather than warning about this the bugs should be fixed, there is no reason why
glibc needs to malloc memory for these cases.  For "%.65535s" I don't actually
see where it would allocate memory, I see memory allocations when it has to
convert between wide and narrow strings or vice versa, for either of these
cases it is enough to put a max cap on the buffer size and just handle it
piecewise rather than all in one go.  For integral numbers with high precision,
again, it is trivial to estimate how many characters you really need, the rest
is just padding which can be handled differently.
>From gcc-bugs-return-630409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:29:57 2019
Return-Path: <gcc-bugs-return-630409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86085 invoked by alias); 23 Jan 2019 07:29:56 -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 86032 invoked by uid 48); 23 Jan 2019 07:29:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBkLzg5MDA0XSBOZXc6IG10eXBlLmM6MjMyOTozMzogZXJyb3I6IGNv?= =?UTF-8?B?bXBhcmlzb24gb2YgaW50ZWdlciBleHByZXNzaW9ucyBvZiBkaWZmZXJlbnQg?= =?UTF-8?B?c2lnbmVkbmVzczog4oCYaW504oCZIGFuZCDigJhzaXplX3TigJkge2FrYSA=?= =?UTF-8?B?4oCYbG9uZyB1bnNpZ25lZCBpbnTigJl9IFstV2Vycm9yPXNpZ24tY29tcGFy?= =?UTF-8?B?ZV0=?Date: Wed, 23 Jan 2019 07:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-89004-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: 2019-01/txt/msg03218.txt.bz2
Content-length: 2319

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

            Bug ID: 89004
           Summary: mtype.c:2329:33: error: comparison of integer
                    expressions of different signedness: â€˜intâ€™ and
                    â€˜size_tâ€™ {aka â€˜long unsigned intâ€™}
                    [-Werror=sign-compare]
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: marxin at gcc dot gnu.org
  Target Milestone: ---

Started with merge from upstream dmd r268124. Full warning:

In file included from ../../gcc/d/d-system.h:23,
                 from ../../gcc/d/dmd/root/dsystem.h:24,
                 from ../../gcc/d/dmd/mtype.c:11:
../../gcc/d/dmd/mtype.c: In member function â€˜Identifier*
Type::getTypeInfoIdent()â€™:
../../gcc/d/dmd/mtype.c:2329:33: error: comparison of integer expressions of
different signedness: â€˜intâ€™ and â€˜size_tâ€™ {aka â€˜long unsigned intâ€™}
[-Werror=sign-compare]
 2329 |     assert(0 < length && length < namelen);     // don't overflow the
buffer
      |                          ~~~~~~~^~~~~~~~~
../../gcc/system.h:742:14: note: in definition of macro â€˜gcc_assertâ€™
  742 |    ((void)(!(EXPR) ? fancy_abort (__FILE__, __LINE__, __FUNCTION__), 0
: 0))
      |              ^~~~
../../gcc/d/dmd/mtype.c:2329:5: note: in expansion of macro â€˜assertâ€™
 2329 |     assert(0 < length && length < namelen);     // don't overflow the
buffer
      |     ^~~~~~

Patch candidate:
diff --git a/gcc/d/dmd/mtype.c b/gcc/d/dmd/mtype.c
index 09161a313ee..2a23cab74fd 100644
--- a/gcc/d/dmd/mtype.c
+++ b/gcc/d/dmd/mtype.c
@@ -2326,7 +2326,7 @@ Identifier *Type::getTypeInfoIdent()

     int length = sprintf(name, "_D%lluTypeInfo_%s6__initZ", (unsigned long
long) 9 + len, buf.data);
     //printf("%p, deco = %s, name = %s\n", this, deco, name);
-    assert(0 < length && length < namelen);     // don't overflow the buffer
+    assert(0 < length && (size_t)length < namelen);     // don't overflow the
buffer

     Identifier *id = Identifier::idPool(name, length);
>From gcc-bugs-return-630410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:31:04 2019
Return-Path: <gcc-bugs-return-630410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87966 invoked by alias); 23 Jan 2019 07:30:56 -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 87652 invoked by uid 48); 23 Jan 2019 07:30:35 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBkLzg5MDA0XSBtdHlwZS5jOjIzMjk6MzM6IGVycm9yOiBjb21wYXJp?= =?UTF-8?B?c29uIG9mIGludGVnZXIgZXhwcmVzc2lvbnMgb2YgZGlmZmVyZW50IHNpZ25l?= =?UTF-8?B?ZG5lc3M6IOKAmGludOKAmSBhbmQg4oCYc2l6ZV904oCZIHtha2Eg4oCYbG9u?= =?UTF-8?B?ZyB1bnNpZ25lZCBpbnTigJl9IFstV2Vycm9yPXNpZ24tY29tcGFyZV0=?Date: Wed, 23 Jan 2019 07:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-89004-4-x8W5CJT88R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89004-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: 2019-01/txt/msg03219.txt.bz2
Content-length: 588

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
                 CC|                            |ibuclaw at gcc dot gnu.org
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1
      Known to fail|                            |9.0
>From gcc-bugs-return-630411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:43:44 2019
Return-Path: <gcc-bugs-return-630411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46998 invoked by alias); 23 Jan 2019 07:43:43 -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 46929 invoked by uid 48); 23 Jan 2019 07:43:40 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBkLzg5MDA0XSBtdHlwZS5jOjIzMjk6MzM6IGVycm9yOiBjb21wYXJp?= =?UTF-8?B?c29uIG9mIGludGVnZXIgZXhwcmVzc2lvbnMgb2YgZGlmZmVyZW50IHNpZ25l?= =?UTF-8?B?ZG5lc3M6IOKAmGludOKAmSBhbmQg4oCYc2l6ZV904oCZIHtha2Eg4oCYbG9u?= =?UTF-8?B?ZyB1bnNpZ25lZCBpbnTigJl9IFstV2Vycm9yPXNpZ24tY29tcGFyZV0=?Date: Wed, 23 Jan 2019 07:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89004-4-MCnFNMtYbX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89004-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: 2019-01/txt/msg03220.txt.bz2
Content-length: 453

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Fixed on trunk in r268167.
>From gcc-bugs-return-630412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:44:21 2019
Return-Path: <gcc-bugs-return-630412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52007 invoked by alias); 23 Jan 2019 07:44: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 49990 invoked by uid 48); 23 Jan 2019 07:44:16 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88993] GCC 9 -Wformat-overflow=2 should reflect real libc limits
Date: Wed, 23 Jan 2019 07:44: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88993-4-Rajm16UNB4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88993-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: 2019-01/txt/msg03221.txt.bz2
Content-length: 870

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

--- Comment #4 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> Rather than warning about this the bugs should be fixed, there is no reason
> why glibc needs to malloc memory for these cases.

I completely agree.  The warning is bogus.  In any case, the trigger point is
much too low.

> For "%.65535s" I don't
> actually see where it would allocate memory, I see memory allocations when
> it has to convert between wide and narrow strings or vice versa, for either
> of these cases it is enough to put a max cap on the buffer size and just
> handle it piecewise rather than all in one go.

There's a patch for that: https://patchwork.sourceware.org/patch/21106/

It needs to be rebased to current master (and perhaps adjusted to use an
overflow-checking builtin).
>From gcc-bugs-return-630413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:47:10 2019
Return-Path: <gcc-bugs-return-630413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30413 invoked by alias); 23 Jan 2019 07:47:09 -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 30380 invoked by uid 48); 23 Jan 2019 07:47:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Wed, 23 Jan 2019 07:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88994-4-sA8iHWH3OS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03222.txt.bz2
Content-length: 704

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-23
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1
      Known to fail|                            |9.0

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, I'm working on that.
>From gcc-bugs-return-630414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 07:51:27 2019
Return-Path: <gcc-bugs-return-630414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89228 invoked by alias); 23 Jan 2019 07:51:27 -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 89155 invoked by uid 48); 23 Jan 2019 07:51:23 -0000
From: "moussu.robin at pm dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Wed, 23 Jan 2019 07:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: moussu.robin at pm dot me
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88994-4-urf6YZNPHy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03223.txt.bz2
Content-length: 179

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

--- Comment #2 from Robin <moussu.robin at pm dot me> ---
Nice :)
Feel free to ask me any additionnal things if it may help.
>From gcc-bugs-return-630415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:03:50 2019
Return-Path: <gcc-bugs-return-630415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32490 invoked by alias); 23 Jan 2019 08:03:49 -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 32438 invoked by uid 48); 23 Jan 2019 08:03:45 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89005] New: [nvptx, libgomp] Too much memory allocated in map_init
Date: Wed, 23 Jan 2019 08:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89005-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: 2019-01/txt/msg03224.txt.bz2
Content-length: 1048

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

            Bug ID: 89005
           Summary: [nvptx, libgomp] Too much memory allocated in map_init
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Before "[nvptx] Remove use of CUDA unified memory in libgomp", in map_init we
allocated a page-sized chunk of page-locked memory, which was used to provide
the memory for all subsequent map_push calls.

After mentioned commit, map_push allocates host and device memory, if needed.
map_init though allocates an initial element, which happens to be ...
paged-sized.

While it's not wrong to allocate an initial element, although it's not clear to
me whether it's beneficial, allocating one of this size is probably overdoing
it.

We should reduce the size of the initial element, or drop it altogether.
>From gcc-bugs-return-630416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:05:33 2019
Return-Path: <gcc-bugs-return-630416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54400 invoked by alias); 23 Jan 2019 08:05:32 -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 43463 invoked by uid 48); 23 Jan 2019 08:05:28 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89005] [nvptx, libgomp] Too much memory allocated in map_init
Date: Wed, 23 Jan 2019 08:05: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89005-4-r8fG9YhMqk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89005-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: 2019-01/txt/msg03225.txt.bz2
Content-length: 1133

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Tentative patch to remove initial element:
...
diff --git a/libgomp/plugin/plugin-nvptx.c b/libgomp/plugin/plugin-nvptx.c
index ff90b67cb86..cbabc8dba96 100644
--- a/libgomp/plugin/plugin-nvptx.c
+++ b/libgomp/plugin/plugin-nvptx.c
@@ -279,11 +279,7 @@ cuda_map_destroy (struct cuda_map *map)
 static bool
 map_init (struct ptx_stream *s)
 {
-  int size = getpagesize ();
-
-  assert (s);
-
-  s->map = cuda_map_create (size);
+  s->map = NULL;

   return true;
 }
@@ -291,9 +287,8 @@ map_init (struct ptx_stream *s)
 static bool
 map_fini (struct ptx_stream *s)
 {
-  assert (s->map->next == NULL);
-
-  cuda_map_destroy (s->map);
+  if (s->map)
+    cuda_map_destroy (s->map);

   return true;
 }
@@ -323,10 +318,9 @@ map_push (struct ptx_stream *s, size_t size)
   struct cuda_map **t;

   assert (s);
-  assert (s->map);

   /* Select an element to push.  */
-  if (s->map->active)
+  if (!s->map || s->map->active)
     map = cuda_map_create (size);
   else
     {
...

Passes libgomp.oacc-c/c.exp
>From gcc-bugs-return-630417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:16:54 2019
Return-Path: <gcc-bugs-return-630417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65177 invoked by alias); 23 Jan 2019 08:16:53 -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 57773 invoked by uid 55); 23 Jan 2019 08:16:49 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87835] nvptx offloading: libgomp.oacc-c-c++-common/asyncwait-1.c execution test intermittently fails at -O2
Date: Wed, 23 Jan 2019 08:16: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-87835-4-rTuVH4C8ij@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87835-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: 2019-01/txt/msg03226.txt.bz2
Content-length: 2358

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

--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Wed Jan 23 08:16:11 2019
New Revision: 268176

URL: https://gcc.gnu.org/viewcvs?rev=268176&root=gcc&view=rev
Log:
[nvptx, libgomp] Fix map_push

The map field of a struct ptx_stream is a FIFO.  The FIFO is implemented as a
single linked list, with pop-from-the-front semantics.

The function map_pop pops an element, either by:
- deallocating the element, if there is more than one element
- or marking the element inactive, if there's only one element

The responsibility of map_push is to push an element to the back, as well as
selecting the element to push, by:
- allocating an element, or
- reusing the element at the front if inactive and big enough, or
- dropping the element at the front if inactive and not big enough, and
  allocating one that's big enough

The current implemention gets at least the first and most basic scenario wrong:

> map = cuda_map_create (size);

We create an element, and assign it to map.

> for (t = s->map; t->next != NULL; t = t->next)
>   ;

We determine the last element in the fifo.

> t->next = map;

We append the new element.

> s->map = map;

But here, we throw away the rest of the FIFO, and declare the FIFO to be just
the new element.

This problem causes the test-case asyncwait-1.c to fail intermittently on some
systems.  The pr87835.c test-case added here is a a minimized and modified
version of asyncwait-1.c (avoiding the kernel construct) that is more likely to
fail.

Fix this by rewriting map_pop more robustly, by:
- seperating the function in two phases: select element, push element
- when reusing or dropping an element, making sure that the element is cleanly
  popped from the queue
- rewriting the push element part in such a way that it can handle all cases
  without needing if statements, such that each line is exercised for each of
  the three cases.

2019-01-23  Tom de Vries  <tdevries@suse.de>

        PR target/87835
        * plugin/plugin-nvptx.c (map_push): Fix adding of allocated element.
        * testsuite/libgomp.oacc-c-c++-common/pr87835.c: New test.

Added:
    trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr87835.c
Modified:
    trunk/libgomp/ChangeLog
    trunk/libgomp/plugin/plugin-nvptx.c
>From gcc-bugs-return-630419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:17:21 2019
Return-Path: <gcc-bugs-return-630419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125291 invoked by alias); 23 Jan 2019 08:17: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 113017 invoked by uid 55); 23 Jan 2019 08:17:17 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88939] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort
Date: Wed, 23 Jan 2019 08:17: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88939-4-l7Ac2K0gKi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88939-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: 2019-01/txt/msg03228.txt.bz2
Content-length: 2610

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Wed Jan 23 08:16:42 2019
New Revision: 268177

URL: https://gcc.gnu.org/viewcvs?rev=268177&root=gcc&view=rev
Log:
[nvptx, libgomp] Fix assert (!s->map->active) in map_fini

There are currently two situations where this assert triggers:
...
libgomp/plugin/plugin-nvptx.c: map_fini: Assertion `!s->map->active' failed.
...

First, in abort-1.c, a parallel region triggering an abort:
...
int
main (void)
{
  #pragma acc parallel
  abort ();

  return 0;
}
...

The abort is detected in nvptx_exec as the CUDA_ERROR_ILLEGAL_INSTRUCTION
return status of the cuStreamSynchronize call after kernel launch, which is
then handled by calling non-returning function GOMP_PLUGIN_fatal.
Consequently, the map_pop in nvptx_exec that in case of cuStreamSynchronize
success would remove or inactive the element added by the map_push earlier in
nvptx_exec, does not trigger.  With the element no longer active, but still
marked active and a member of s->map,  we run into the assert during
GOMP_OFFLOAD_fini_device, which is triggered from atexit handler
gomp_target_fini (which is triggered by the GOMP_PLUGIN_fatal mentioned above
calling exit).

Second, in pr88941.c, an async parallel region without wait:
...
int
main (void)
{
  #pragma acc parallel async
  ;

  /* no #pragma acc wait */
  return 0;
}
...

Because nvptx_exec is handling an async region, it does not call map_pop for
the element added by map_push, but schedules an kernel execution completion
event to call map_pop.  Again, we run into the assert during
GOMP_OFFLOAD_fini_device, which is triggered from atexit handler
gomp_target_fini, but the exit in this case is triggered by returning from
main.
So either the kernel is still running, or the kernel has completed but the
corresponding event that is supposed to call map_pop is stuck in the event
queue, waiting for an event_gc.

Fix this by removing the assert, and skipping the freeing of device memory if
the map is still marked active (though in the async case, this is more a
workaround than an fix).

2019-01-23  Tom de Vries  <tdevries@suse.de>

        PR target/88941
        PR target/88939
        * plugin/plugin-nvptx.c (cuda_map_destroy): Handle map->active case.
        (map_fini): Remove "assert (!s->map->active)".
        * testsuite/libgomp.oacc-c-c++-common/pr88941.c: New test.

Added:
    trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr88941.c
Modified:
    trunk/libgomp/ChangeLog
    trunk/libgomp/plugin/plugin-nvptx.c
>From gcc-bugs-return-630418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:17:21 2019
Return-Path: <gcc-bugs-return-630418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124041 invoked by alias); 23 Jan 2019 08:17: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 111696 invoked by uid 55); 23 Jan 2019 08:17:16 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88941] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel
Date: Wed, 23 Jan 2019 08:17: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88941-4-V3sgv6d9MC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88941-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: 2019-01/txt/msg03227.txt.bz2
Content-length: 2610

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Wed Jan 23 08:16:42 2019
New Revision: 268177

URL: https://gcc.gnu.org/viewcvs?rev=268177&root=gcc&view=rev
Log:
[nvptx, libgomp] Fix assert (!s->map->active) in map_fini

There are currently two situations where this assert triggers:
...
libgomp/plugin/plugin-nvptx.c: map_fini: Assertion `!s->map->active' failed.
...

First, in abort-1.c, a parallel region triggering an abort:
...
int
main (void)
{
  #pragma acc parallel
  abort ();

  return 0;
}
...

The abort is detected in nvptx_exec as the CUDA_ERROR_ILLEGAL_INSTRUCTION
return status of the cuStreamSynchronize call after kernel launch, which is
then handled by calling non-returning function GOMP_PLUGIN_fatal.
Consequently, the map_pop in nvptx_exec that in case of cuStreamSynchronize
success would remove or inactive the element added by the map_push earlier in
nvptx_exec, does not trigger.  With the element no longer active, but still
marked active and a member of s->map,  we run into the assert during
GOMP_OFFLOAD_fini_device, which is triggered from atexit handler
gomp_target_fini (which is triggered by the GOMP_PLUGIN_fatal mentioned above
calling exit).

Second, in pr88941.c, an async parallel region without wait:
...
int
main (void)
{
  #pragma acc parallel async
  ;

  /* no #pragma acc wait */
  return 0;
}
...

Because nvptx_exec is handling an async region, it does not call map_pop for
the element added by map_push, but schedules an kernel execution completion
event to call map_pop.  Again, we run into the assert during
GOMP_OFFLOAD_fini_device, which is triggered from atexit handler
gomp_target_fini, but the exit in this case is triggered by returning from
main.
So either the kernel is still running, or the kernel has completed but the
corresponding event that is supposed to call map_pop is stuck in the event
queue, waiting for an event_gc.

Fix this by removing the assert, and skipping the freeing of device memory if
the map is still marked active (though in the async case, this is more a
workaround than an fix).

2019-01-23  Tom de Vries  <tdevries@suse.de>

        PR target/88941
        PR target/88939
        * plugin/plugin-nvptx.c (cuda_map_destroy): Handle map->active case.
        (map_fini): Remove "assert (!s->map->active)".
        * testsuite/libgomp.oacc-c-c++-common/pr88941.c: New test.

Added:
    trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr88941.c
Modified:
    trunk/libgomp/ChangeLog
    trunk/libgomp/plugin/plugin-nvptx.c
>From gcc-bugs-return-630420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:33:13 2019
Return-Path: <gcc-bugs-return-630420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93107 invoked by alias); 23 Jan 2019 08:33:13 -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 93004 invoked by uid 48); 23 Jan 2019 08:33:09 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87835] nvptx offloading: libgomp.oacc-c-c++-common/asyncwait-1.c execution test intermittently fails at -O2
Date: Wed, 23 Jan 2019 08:33: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone
Message-ID: <bug-87835-4-C98XYiR5DZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87835-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: 2019-01/txt/msg03229.txt.bz2
Content-length: 605

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
           Assignee|unassigned at gcc dot gnu.org      |vries at gcc dot gnu.org
   Target Milestone|---                         |9.0

--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch and test-case committed, marking resolved fixed.
>From gcc-bugs-return-630421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:36:14 2019
Return-Path: <gcc-bugs-return-630421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105246 invoked by alias); 23 Jan 2019 08:36:14 -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 105162 invoked by uid 55); 23 Jan 2019 08:36:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Wed, 23 Jan 2019 08:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88964-4-y9XD4XNqld@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03230.txt.bz2
Content-length: 699

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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 23 08:35:38 2019
New Revision: 268179

URL: https://gcc.gnu.org/viewcvs?rev=268179&root=gcc&view=rev
Log:
        PR tree-optimization/88964
        * gimple-loop-interchange.cc (loop_cand::analyze_induction_var): Use
        build_zero_cst instead of build_int_cst.  Return false for loop
        invariants which honor signed zeros.

        * gfortran.dg/pr88964.f90: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/pr88964.f90
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/gimple-loop-interchange.cc
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:37:20 2019
Return-Path: <gcc-bugs-return-630422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110923 invoked by alias); 23 Jan 2019 08:37:19 -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 108458 invoked by uid 48); 23 Jan 2019 08:37:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88964] [8 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Wed, 23 Jan 2019 08:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88964-4-JunWlyXgOl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88964-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: 2019-01/txt/msg03231.txt.bz2
Content-length: 535

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[8/9 Regression] ICE in     |[8 Regression] ICE in
                   |wide_int_to_tree_1, at      |wide_int_to_tree_1, at
                   |tree.c:1561                 |tree.c:1561

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-630423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:37:48 2019
Return-Path: <gcc-bugs-return-630423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17874 invoked by alias); 23 Jan 2019 08:37: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 10759 invoked by uid 48); 23 Jan 2019 08:37:42 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88939] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for synchronous parallel with abort
Date: Wed, 23 Jan 2019 08:37: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone
Message-ID: <bug-88939-4-xCCpeAHqJ3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88939-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: 2019-01/txt/msg03232.txt.bz2
Content-length: 797

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
           Assignee|unassigned at gcc dot gnu.org      |vries at gcc dot gnu.org
   Target Milestone|---                         |9.0

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch committed.

Test-case that triggered this PR is already in the sources, but unfortunately
we don't have dg-output-not to test that the assert is not triggered, so the
test-case won't regress if the assert returns.

Marking resolved fixed.
>From gcc-bugs-return-630424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:39:08 2019
Return-Path: <gcc-bugs-return-630424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47574 invoked by alias); 23 Jan 2019 08:39:07 -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 39171 invoked by uid 48); 23 Jan 2019 08:39:03 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88941] [nvptx, openacc, libgomp] Assertion `!s->map->active' failed for empty asynchronous parallel
Date: Wed, 23 Jan 2019 08:39: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone
Message-ID: <bug-88941-4-F2bfRgJYjx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88941-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: 2019-01/txt/msg03233.txt.bz2
Content-length: 605

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
           Assignee|unassigned at gcc dot gnu.org      |vries at gcc dot gnu.org
   Target Milestone|---                         |9.0

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch and test-case committed, marking resolved fixed.
>From gcc-bugs-return-630425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:41:50 2019
Return-Path: <gcc-bugs-return-630425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37871 invoked by alias); 23 Jan 2019 08:41:49 -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 28816 invoked by uid 48); 23 Jan 2019 08:41:46 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88974] [9 Regression] ICE: Segmentation fault (in linemap_resolve_location)
Date: Wed, 23 Jan 2019 08:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88974-4-ICPFVRIDjR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88974-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: 2019-01/txt/msg03234.txt.bz2
Content-length: 293

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |9.0
>From gcc-bugs-return-630427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:42:40 2019
Return-Path: <gcc-bugs-return-630427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18878 invoked by alias); 23 Jan 2019 08:42:39 -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 6626 invoked by uid 48); 23 Jan 2019 08:42:34 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88946] [nvptx, openacc, libgomp] cuMemAlloc error for two empty asynchronous parallels
Date: Wed, 23 Jan 2019 08:42: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88946-4-dMleTDO98Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88946-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88946-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: 2019-01/txt/msg03236.txt.bz2
Content-length: 470

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch with test-case committed, marking resolved-fixed.
>From gcc-bugs-return-630426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:42:04 2019
Return-Path: <gcc-bugs-return-630426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58828 invoked by alias); 23 Jan 2019 08:42:03 -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 50352 invoked by uid 48); 23 Jan 2019 08:41:59 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88946] [nvptx, openacc, libgomp] cuMemAlloc error for two empty asynchronous parallels
Date: Wed, 23 Jan 2019 08:42: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: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to target_milestone
Message-ID: <bug-88946-4-WFsFNC6WDz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88946-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88946-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: 2019-01/txt/msg03235.txt.bz2
Content-length: 1808

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |vries at gcc dot gnu.org
   Target Milestone|---                         |9.0

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
https://gcc.gnu.org/ml/gcc-cvs/2019-01/msg00697.html:

Author: vries
Date: Wed Jan 23 08:16:56 2019
New Revision: 268178

URL: https://gcc.gnu.org/viewcvs?rev=268178&root=gcc&view=rev
Log:
[nvptx, libgomp] Fix cuMemAlloc with size zero

Consider test-case:
...
int
main (void)
{
  #pragma acc parallel async
  ;
  #pragma acc parallel async
  ;
  #pragma acc wait

  return 0;
}
...

This fails with:
...
libgomp: cuMemAlloc error: invalid argument
Segmentation fault (core dumped)
...
The cuMemAlloc error is due to the fact that we're try to allocate 0 bytes.

Fix this by preventing calling map_push with size zero argument in nvptx_exec.

This also has the consequence that for the abort-1.c test-case, we end up
calling cuMemFree during map_fini for the struct cuda_map allocated in
map_init, which fails because an abort happened.  Fix this by calling
cuMemFree with CUDA_CALL_NOCHECK in cuda_map_destroy.

2019-01-23  Tom de Vries  <tdevries@suse.de>

        PR target/PR88946
        * plugin/plugin-nvptx.c (cuda_map_destroy): Use CUDA_CALL_NOCHECK for
        cuMemFree.
        (nvptx_exec): Don't call map_push if mapnum == 0.
        * testsuite/libgomp.oacc-c-c++-common/pr88946.c: New test.

Added:
    trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr88946.c
Modified:
    trunk/libgomp/ChangeLog
    trunk/libgomp/plugin/plugin-nvptx.c
>From gcc-bugs-return-630429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:43:44 2019
Return-Path: <gcc-bugs-return-630429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4283 invoked by alias); 23 Jan 2019 08:43:44 -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 124061 invoked by uid 48); 23 Jan 2019 08:43:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88980] [9 regression] segfault on allocatable string member assignment
Date: Wed, 23 Jan 2019 08:43: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88980-4-yTJwWViLlc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88980-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: 2019-01/txt/msg03238.txt.bz2
Content-length: 345

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P4
   Target Milestone|---                         |9.0
>From gcc-bugs-return-630428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:43:06 2019
Return-Path: <gcc-bugs-return-630428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67371 invoked by alias); 23 Jan 2019 08:43:06 -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 57711 invoked by uid 48); 23 Jan 2019 08:43:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88976] [7/8/9 Regression] ICE in fold_convert_loc, at fold-const.c:2552
Date: Wed, 23 Jan 2019 08:43: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority version target_milestone short_desc
Message-ID: <bug-88976-4-qClzjXtrEO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88976-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88976-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: 2019-01/txt/msg03237.txt.bz2
Content-length: 610

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
            Version|4.9.0                       |9.0
   Target Milestone|---                         |7.5
            Summary|ICE in fold_convert_loc, at |[7/8/9 Regression] ICE in
                   |fold-const.c:2552           |fold_convert_loc, at
                   |                            |fold-const.c:2552
>From gcc-bugs-return-630430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:46:10 2019
Return-Path: <gcc-bugs-return-630430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22731 invoked by alias); 23 Jan 2019 08:45:58 -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 22460 invoked by uid 48); 23 Jan 2019 08:45:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/89006] New: [9 Regression] New note: non-delegitimized UNSPEC UNSPEC_SET_GOT (14) found in variable location since r267638
Date: Wed, 23 Jan 2019 08:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89006-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: 2019-01/txt/msg03239.txt.bz2
Content-length: 1014

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

            Bug ID: 89006
           Summary: [9 Regression] New note: non-delegitimized UNSPEC
                    UNSPEC_SET_GOT (14) found in variable location since
                    r267638
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
  Target Milestone: ---

Following code snippet is newly diagnosed:

$ cat /tmp/ubsan_flags.ii
class a {
public:
  a(bool);
};
static void b(const char *p1) { new a(p1); }
void c() {
  b("");
  b("Used to provide fuzzing signal without blowing up logs.");
}

$ ./xgcc -B. /tmp/ubsan_flags.ii -c -O2 -g -fPIC -m32
/tmp/ubsan_flags.ii: In function â€˜void c()â€™:
/tmp/ubsan_flags.ii:6:6: note: non-delegitimized UNSPEC UNSPEC_SET_GOT (14)
found in variable location
    6 | void c() {
      |      ^
>From gcc-bugs-return-630432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:46:28 2019
Return-Path: <gcc-bugs-return-630432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23058 invoked by alias); 23 Jan 2019 08:46:11 -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 22498 invoked by uid 48); 23 Jan 2019 08:45:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88985] [9 Regression] ICE in estimate_edge_devirt_benefit, at ipa-fnsummary.c:2585
Date: Wed, 23 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88985-4-1ZUtzviqYz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88985-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: 2019-01/txt/msg03242.txt.bz2
Content-length: 345

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
   Target Milestone|---                         |9.0
>From gcc-bugs-return-630433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:46:29 2019
Return-Path: <gcc-bugs-return-630433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35883 invoked by alias); 23 Jan 2019 08:46:28 -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 22889 invoked by uid 48); 23 Jan 2019 08:46:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88987] [9 Regression] ICE: unexpected expression '(bool)sm' of kind implicit_conv_expr
Date: Wed, 23 Jan 2019 08:46: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: 9.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-88987-4-SDzKXQU59v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88987-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88987-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: 2019-01/txt/msg03241.txt.bz2
Content-length: 356

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |error-recovery
           Priority|P3                          |P4
>From gcc-bugs-return-630431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:46:10 2019
Return-Path: <gcc-bugs-return-630431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22873 invoked by alias); 23 Jan 2019 08:46:08 -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 22547 invoked by uid 48); 23 Jan 2019 08:45:51 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88986] [7/8/9 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in member_vec_binary_search, at cp/name-lookup.c:1136
Date: Wed, 23 Jan 2019 08:46: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: 9.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-88986-4-hAnURV9SHH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88986-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88986-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: 2019-01/txt/msg03240.txt.bz2
Content-length: 356

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |error-recovery
           Priority|P3                          |P4
>From gcc-bugs-return-630434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:46:34 2019
Return-Path: <gcc-bugs-return-630434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37896 invoked by alias); 23 Jan 2019 08:46:33 -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 35366 invoked by uid 48); 23 Jan 2019 08:46:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88988] [8/9 Regression] ICE: Segmentation fault (in lookup_name_real_1)
Date: Wed, 23 Jan 2019 08:46: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: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88988-4-uh0FXi1wOW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88988-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88988-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: 2019-01/txt/msg03243.txt.bz2
Content-length: 345

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
   Target Milestone|---                         |8.3
>From gcc-bugs-return-630436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:47:33 2019
Return-Path: <gcc-bugs-return-630436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97055 invoked by alias); 23 Jan 2019 08:47:30 -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 86585 invoked by uid 48); 23 Jan 2019 08:47:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88995] [8/9 Regression] internal compiler error: in lookup_template_class_1, at cp/pt.c:9471
Date: Wed, 23 Jan 2019 08:47: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cf_known_to_fail
Message-ID: <bug-88995-4-wIZ6MQdik1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88995-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: 2019-01/txt/msg03245.txt.bz2
Content-length: 347

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
      Known to fail|                            |8.2.1
>From gcc-bugs-return-630435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:47:08 2019
Return-Path: <gcc-bugs-return-630435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57232 invoked by alias); 23 Jan 2019 08:47:07 -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 52099 invoked by uid 48); 23 Jan 2019 08:47:03 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/89006] [9 Regression] New note: non-delegitimized UNSPEC UNSPEC_SET_GOT (14) found in variable location since r267638
Date: Wed, 23 Jan 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-89006-4-5n0B0BTxEp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89006-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89006-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: 2019-01/txt/msg03244.txt.bz2
Content-length: 675

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-23
                 CC|                            |gerald at pfeifer dot com
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
   Target Milestone|---                         |9.0
     Ever confirmed|0                           |1
      Known to fail|                            |9.0
>From gcc-bugs-return-630437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:51:11 2019
Return-Path: <gcc-bugs-return-630437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71273 invoked by alias); 23 Jan 2019 08:51: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 59031 invoked by uid 48); 23 Jan 2019 08:51:06 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87306] test case gcc.dg/vect/bb-slp-pow-1.c fails with its introduction in r263290
Date: Wed, 23 Jan 2019 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87306-4-uaxyHMd5wP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87306-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: 2019-01/txt/msg03246.txt.bz2
Content-length: 469

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

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Kewen Lin <linkw at gcc dot gnu.org> ---
The issue should be fixed in trunk. Don't need to back port.
>From gcc-bugs-return-630438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:53:08 2019
Return-Path: <gcc-bugs-return-630438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64922 invoked by alias); 23 Jan 2019 08:53:07 -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 64904 invoked by uid 48); 23 Jan 2019 08:53:02 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89007] New: Implement generic vector average expansion
Date: Wed, 23 Jan 2019 08:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89007-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: 2019-01/txt/msg03247.txt.bz2
Content-length: 2081

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

            Bug ID: 89007
           Summary: Implement generic vector average expansion
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ktkachov at gcc dot gnu.org
  Target Milestone: ---

GCC 9 knows how to recognise vector average operations since PR 85694. Some
targets have optabs to do it in one instruction.

For the targets that don't, we could still do better than the fallback widening
-> arithmetic -> narrowing sequence though. Maybe we could implement a generic
expansion for the case when there is no target optab.

For example:
#define N 1024
unsigned char dst[N];
unsigned char in1[N];
unsigned char in2[N];

void
foo ()
{
  for( int x = 0; x < N; x++ )
    dst[x] = (in1[x] + in2[x] + 1) >> 1;
}

For aarch64 -march=armv8-a+sve -O3 we generate:
.L2:
        ld1b    z0.b, p0/z, [x5, x0]
        ld1b    z2.b, p0/z, [x4, x0]
        uunpklo z1.h, z0.b
        uunpklo z3.h, z2.b
        uunpkhi z0.h, z0.b
        uunpkhi z2.h, z2.b
        add     z1.h, z1.h, z3.h
        add     z0.h, z0.h, z2.h
        add     z1.h, z1.h, #1
        add     z0.h, z0.h, #1
        lsr     z1.h, z1.h, #1
        lsr     z0.h, z0.h, #1
        uzp1    z0.b, z1.b, z0.b
        st1b    z0.b, p0, [x2, x0]
        incb    x0
        whilelo p0.b, x0, x3
        bne     .L2


But we could generate the more optimal:
    ld1b    {z0.b}, p0/z, [x0, x4]
    ld1b    {z2.b}, p0/z, [x1, x4]
    orr     z4.d, z0.d, z2.d         // use and for floor rounding
    and     z4.b, z4.b, #1
    lsr     z0.b, z0.b, #1            // use asr for signed numbers
    lsr     z2.b, z2.b, #1            // likewise
    add     z0.b, z0.b, z2.b
    add     z0.b, z0.b, z4.b
    st1b    {z0.b}, p0, [x2, x4]

I think this doesn't require too much fancy target support, just some vector
masking operations
>From gcc-bugs-return-630440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:57:54 2019
Return-Path: <gcc-bugs-return-630440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9466 invoked by alias); 23 Jan 2019 08:57:53 -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 470 invoked by uid 48); 23 Jan 2019 08:57:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88999] [9 Regression] testcases using in_avail() fail on nios2-elf
Date: Wed, 23 Jan 2019 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget target_milestone
Message-ID: <bug-88999-4-RppK158BhK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88999-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88999-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: 2019-01/txt/msg03249.txt.bz2
Content-length: 352

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |nios2-elf
   Target Milestone|---                         |9.0
>From gcc-bugs-return-630439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:57:08 2019
Return-Path: <gcc-bugs-return-630439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77794 invoked by alias); 23 Jan 2019 08:57:08 -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 77742 invoked by uid 48); 23 Jan 2019 08:57:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88998] [7/8/9 Regression] bad codegen with mmx instructions for unordered_map
Date: Wed, 23 Jan 2019 08:57: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-88998-4-ZThC8ZcGfm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88998-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: 2019-01/txt/msg03248.txt.bz2
Content-length: 1076

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
           Priority|P3                          |P2
      Known to work|                            |6.4.0
   Target Milestone|---                         |7.5
            Summary|bad codegen with mmx        |[7/8/9 Regression] bad
                   |instructions for            |codegen with mmx
                   |unordered_map               |instructions for
                   |                            |unordered_map
      Known to fail|                            |7.3.1, 8.2.1, 9.0

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, I see no explicit MMX reg/intrinsic uses in the testcase if I am not
mistaken so the compiler should not end up using MMX.

GCC 6 "failed" to do this optimization, but the issue might have been latent
there.
>From gcc-bugs-return-630441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 08:59:20 2019
Return-Path: <gcc-bugs-return-630441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18818 invoked by alias); 23 Jan 2019 08:59: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 6625 invoked by uid 48); 23 Jan 2019 08:59:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89001] g++ uses wrong mangling for lifetime-extended temporaries
Date: Wed, 23 Jan 2019 08:59: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: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: keywords bug_status cf_reconfirmed_on version everconfirmed cf_known_to_fail
Message-ID: <bug-89001-4-Ax9c6fhfjJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89001-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89001-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: 2019-01/txt/msg03250.txt.bz2
Content-length: 700

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ABI
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
            Version|unknown                     |9.0
     Ever confirmed|0                           |1
      Known to fail|                            |7.3.1, 8.2.1, 9.0

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC behaves like this since the feature is supported.
>From gcc-bugs-return-630442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:01:07 2019
Return-Path: <gcc-bugs-return-630442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91215 invoked by alias); 23 Jan 2019 09:00:39 -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 90384 invoked by uid 48); 23 Jan 2019 09:00:11 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89002] [7/8/9 Regression] ICE in scan_omp_1_op, at omp-low.c:3166
Date: Wed, 23 Jan 2019 09:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority version target_milestone short_desc
Message-ID: <bug-89002-4-mpTxnSIbf2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89002-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89002-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: 2019-01/txt/msg03251.txt.bz2
Content-length: 604

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
            Version|5.0                         |9.0
   Target Milestone|---                         |9.0
            Summary|ICE in scan_omp_1_op, at    |[7/8/9 Regression] ICE in
                   |omp-low.c:3166              |scan_omp_1_op, at
                   |                            |omp-low.c:3166
>From gcc-bugs-return-630443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:06:30 2019
Return-Path: <gcc-bugs-return-630443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90161 invoked by alias); 23 Jan 2019 09:06:30 -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 67392 invoked by uid 48); 23 Jan 2019 09:06:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89003] Return inside a statement expression while initializing a static local variable fails to cleanup cxa_guard
Date: Wed, 23 Jan 2019 09:06: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: 5.4.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords cf_known_to_fail
Message-ID: <bug-89003-4-GK61WUx9Sm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89003-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: 2019-01/txt/msg03252.txt.bz2
Content-length: 1532

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
      Known to fail|                            |8.2.1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.

  _2 = __cxa_guard_acquire (&_ZGVZ1fvE1i);
  retval.1 = _2 != 0;
  if (retval.1 != 0) goto <D.2375>; else goto <D.2376>;
  <D.2375>:
  D.2370 = 0;
  try
    {
      return;
      i = 42;
      D.2370 = 1;
      __cxa_guard_release (&_ZGVZ1fvE1i);
    }
  catch
    {
      if (D.2370 != 0) goto <D.2377>; else goto <D.2378>;
      <D.2377>:
      goto <D.2379>;
      <D.2378>:
      __cxa_guard_abort (&_ZGVZ1fvE1i);
      <D.2379>:
    }

Docs for statement expressions say

"Jumping out of a statement expression is permitted, but if the
statement expression is part of a larger expression then it is
unspecified which other subexpressions of that expression have been
evaluated except where the language definition requires certain
subexpressions to be evaluated before or after the statement
expression."

so I'd say it behaves as documented since the statement expression is
part of an initialization expression which involves locking (though
not sure if that part is mandated by the standard and thus this
implementation detail shouldn't trigger the unspecified behavior).
>From gcc-bugs-return-630444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:25:02 2019
Return-Path: <gcc-bugs-return-630444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8343 invoked by alias); 23 Jan 2019 09:24:48 -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 129343 invoked by uid 48); 23 Jan 2019 09:24:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/89000] gcov --function-summaries says No branches/No calls, only the File summary is correct
Date: Wed, 23 Jan 2019 09:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-89000-4-aRyIHuPPMM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89000-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89000-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: 2019-01/txt/msg03253.txt.bz2
Content-length: 1032

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-23
      Known to work|                            |7.3.0
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org
   Target Milestone|---                         |10.0
     Ever confirmed|0                           |1
      Known to fail|                            |8.2.0, 9.0

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
I can confirm that, it's related to more complex function handling.
I incline to remove the --function-summaries and compute the info for
intermediate format so that one can use it in a tool.
As mentioned, normal output is correct and one can compute the information.
Steve, does it work for you?
>From gcc-bugs-return-630445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:27:24 2019
Return-Path: <gcc-bugs-return-630445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1227 invoked by alias); 23 Jan 2019 09:27:24 -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 127862 invoked by uid 48); 23 Jan 2019 09:27:20 -0000
From: "konstantin.vladimirov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] New: O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: konstantin.vladimirov at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89008-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: 2019-01/txt/msg03254.txt.bz2
Content-length: 1759

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

            Bug ID: 89008
           Summary: O2 and O1 results differ for simple test
           Product: gcc
           Version: 8.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: konstantin.vladimirov at gmail dot com
  Target Milestone: ---

Simple test:

----
#include <stdlib.h>

unsigned long a, c;
unsigned b;
int d, e;
long f() {
  unsigned long g = 0;
  for (d = 0; d < 5; d += 2)
    for (e = 0; e < 5; e += 3) {
      c = 4 + b;
      g = -b - b;
      b = 5 * (b << 24);
    }
  a = g;
  return 0;
}

int main() {
  f();
  if (a)
    abort();
}
---

Obviously, b initially 0 and 5*(b<<24) is 0 too on every iteration. But compile
and run it with gcc 8.1

> gcc -O1 min-05.c
> a.out
> gcc -O2 min-05.c
> a.out
Aborted

Compiler information:

> gcc --verbose
COLLECT_GCC=/apps/gcc/8.1.0/.bin/gcc
COLLECT_LTO_WRAPPER=/apps/gcc/8.1.0/.bin/../libexec/gcc/x86_64-suse-linux/8.1.0/lto-wrapper
Target: x86_64-suse-linux
Configured with: ./configure --prefix=/apps/gcc/8.1.0
--libdir=/apps/gcc/8.1.0/lib64 --libexecdir=/apps/gcc/8.1.0/libexec
--bindir=/apps/gcc/8.1.0/bin --with-isl=/apps/gcc/8.1.0
--with-libelf=/apps/gcc/8.1.0 --with-mpfr=/apps/gcc/8.1.0
--with-gmp=/apps/gcc/8.1.0 --with-mpc=/apps/gcc/8.1.0
--disable-gnu-unique-object --enable-gold=yes --enable-lto
--enable-languages=c,c++,objc,fortran --build=x86_64-suse-linux
--host=x86_64-suse-linux --target=x86_64-suse-linux --enable-libotm
--disable-multilib --disable-bootstrap --disable-libstdcxx-pch
Thread model: posix
gcc version 8.1.0 (GCC)
>From gcc-bugs-return-630446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:31:17 2019
Return-Path: <gcc-bugs-return-630446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52806 invoked by alias); 23 Jan 2019 09:31:16 -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 43364 invoked by uid 48); 23 Jan 2019 09:31:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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-88713-4-whjJsJF4u9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03255.txt.bz2
Content-length: 2298

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl.tools at gmail dot com

--- Comment #34 from Richard Biener <rguenth at gcc dot gnu.org> ---
So with -Ofast and -mprefer-vector-width=256 I get

  <bb 2> [local count: 63136019]:
  vect__4.2_3 = MEM[(float *)a_11(D)];
  vect__5.3_4 = RSQRT (vect__4.2_3);
  MEM[(float *)r_12(D)] = vect__5.3_4;
  vect__4.2_21 = MEM[(float *)a_11(D) + 32B];
  vect__5.3_20 = RSQRT (vect__4.2_21);
  MEM[(float *)r_12(D) + 32B] = vect__5.3_20;

while with -mprefer-vector-width=512 I need -mavx512er to trigger the
expander, then I also get

  <bb 2> [local count: 63136020]:
  vect__4.2_21 = MEM[(float *)a_11(D)];
  vect__5.3_20 = RSQRT (vect__4.2_21);
  MEM[(float *)r_12(D)] = vect__5.3_20;

and in that case

rsqrt:
.LFB12:
        .cfi_startproc
        vrsqrt28ps      (%rsi), %zmm0
        vmovups %zmm0, (%rdi)
        vzeroupper
        ret

(huh?  isn't there a NR step missing?)

for -mprefer-vector-width=256 I get (irrespective of -mavx512er):

rsqrt:
.LFB12:
        .cfi_startproc
        vmovups (%rsi), %ymm1
        vmovaps .LC1(%rip), %ymm3
        vrsqrtps        %ymm1, %ymm2
        vmovaps .LC0(%rip), %ymm4
        vmovups 32(%rsi), %ymm0
        vmulps  %ymm1, %ymm2, %ymm1
        vmulps  %ymm2, %ymm1, %ymm1
        vmulps  %ymm3, %ymm2, %ymm2
        vaddps  %ymm4, %ymm1, %ymm1
        vmulps  %ymm2, %ymm1, %ymm1
        vmovups %ymm1, (%rdi)
        vrsqrtps        %ymm0, %ymm1
        vmulps  %ymm0, %ymm1, %ymm0
        vmulps  %ymm1, %ymm0, %ymm0
        vmulps  %ymm3, %ymm1, %ymm1
        vaddps  %ymm4, %ymm0, %ymm0
        vmulps  %ymm1, %ymm0, %ymm0
        vmovups %ymm0, 32(%rdi)
        vzeroupper

so the issue lies somewhere in the backend.

Of the "fast" you need -ffinite-math-only -fno-math-errno
-funsafe-math-optimizations.

GCC definitely fails to see the FMA use as opportunity in
ix86_emit_swsqrtsf, the a == 0 checking is because of the missing
expander w/o avx512er where we could still use the NR sequence
with the other instruction.  HJ?
>From gcc-bugs-return-630447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:32:21 2019
Return-Path: <gcc-bugs-return-630447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116298 invoked by alias); 23 Jan 2019 09:32: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 105522 invoked by uid 48); 23 Jan 2019 09:32:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Wed, 23 Jan 2019 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88994-4-XzGL9CWapv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03256.txt.bz2
Content-length: 327

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

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
(In reply to Robin from comment #2)
> Nice :)
> Feel free to ask me any additionnal things if it may help.

I guess I've got it.
Patch candidate:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01350.html
>From gcc-bugs-return-630448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 09:45:48 2019
Return-Path: <gcc-bugs-return-630448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108393 invoked by alias); 23 Jan 2019 09:45:47 -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 80888 invoked by uid 48); 23 Jan 2019 09:45:20 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88999] [9 Regression] testcases using in_avail() fail on nios2-elf
Date: Wed, 23 Jan 2019 09:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88999-4-VFESs49Pbm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88999-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88999-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: 2019-01/txt/msg03257.txt.bz2
Content-length: 953

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to sandra from comment #0)
> I see that these tests are xfailed for bare-metal ARM targets with a note
> that ARM semihosting doesn't support the underlying fstat call, but that is
> not true of nios2.  These tests all passed on nios2-elf with GCC 8.

I see no relevant changes on trunk compared to gcc-8-branch.

> I realize it is hard for other people to test this target, but I'd be happy
> to test a patch or do some debugging to try to track it down given some
> clues about where to look.  (Maybe this failure rings a bell with someone
> already familiar with the code?)

This should cover all the relevant code (and a few more bits) and doesn't show
anything that looks relevant:

  git diff gcc-8-branch master  -- config/io/  src/c++??/*stream* \
    include/{bits,std}/*stream*  include/ext/stdio*filebuf.h
>From gcc-bugs-return-630449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:02:40 2019
Return-Path: <gcc-bugs-return-630449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108817 invoked by alias); 23 Jan 2019 10:02:39 -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 103285 invoked by uid 48); 23 Jan 2019 10:02:35 -0000
From: "florian.schornbaum at siemens dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88531] Index data types when targeting AVX-512 vectorization with gather/scatter
Date: Wed, 23 Jan 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: florian.schornbaum at siemens dot com
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:
Message-ID: <bug-88531-4-4zMXYjY9KW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88531-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: 2019-01/txt/msg03258.txt.bz2
Content-length: 457

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

--- Comment #6 from Florian Schornbaum <florian.schornbaum at siemens dot com> ---
Thanks Jakub. That's good information to have.

We would certainly be willing to help since this is something that we would
really like GCC to be able to handle.

Does it make sense for us, as developers that have never been involved in GCC
development, to have a look if you give as some pointers on where to look?
>From gcc-bugs-return-630450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:03:41 2019
Return-Path: <gcc-bugs-return-630450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21930 invoked by alias); 23 Jan 2019 10:03:40 -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 6951 invoked by uid 48); 23 Jan 2019 10:03:35 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88998] [7/8/9 Regression] bad codegen with mmx instructions for unordered_map
Date: Wed, 23 Jan 2019 10:03: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88998-4-zXrvyqpFH9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88998-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: 2019-01/txt/msg03259.txt.bz2
Content-length: 972

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

UroÅ¡ Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |ubizjak at gmail dot com

--- Comment #4 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Created attachment 45503
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45503&action=edit
Proposed patch

We can use cvtdq2pd instead of cvtpi2pd and directly use xmm input register.
The  patched compiler generates:

        vmovd   %edi, %xmm1
        vpinsrd $1, %esi, %xmm1, %xmm0
        vcvtdq2pd       %xmm0, %xmm0
        vhaddpd %xmm0, %xmm0, %xmm0
        ret

which avoids MMX registers altogether.

The patch also amends cvtpd2pi/cvttpd2pi in a similar way, so it can output
directly to xmm register.
>From gcc-bugs-return-630451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:06:13 2019
Return-Path: <gcc-bugs-return-630451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75527 invoked by alias); 23 Jan 2019 10:06:12 -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 62915 invoked by uid 48); 23 Jan 2019 10:06:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88531] Index data types when targeting AVX-512 vectorization with gather/scatter
Date: Wed, 23 Jan 2019 10:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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:
Message-ID: <bug-88531-4-EjVRaOobeJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88531-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: 2019-01/txt/msg03260.txt.bz2
Content-length: 656

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

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Florian Schornbaum from comment #6)
> Thanks Jakub. That's good information to have.
> 
> We would certainly be willing to help since this is something that we would
> really like GCC to be able to handle.
> 
> Does it make sense for us, as developers that have never been involved in
> GCC development, to have a look if you give as some pointers on where to
> look?

Since Mentor and thus CodeSourcery is now part of the Siemens family you
could even get support for this from various GCC maintainers in-house ;)
>From gcc-bugs-return-630452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:09:40 2019
Return-Path: <gcc-bugs-return-630452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7561 invoked by alias); 23 Jan 2019 10:09:40 -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 127524 invoked by uid 48); 23 Jan 2019 10:09:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88933-4-CtRdV7QDII@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03261.txt.bz2
Content-length: 300

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

--- Comment #7 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Created attachment 45504
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45504&action=edit
Untested patch candidate

@Martin: Can you please take a look at the patch?
>From gcc-bugs-return-630453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:11:30 2019
Return-Path: <gcc-bugs-return-630453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2968 invoked by alias); 23 Jan 2019 10:11:29 -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 127124 invoked by uid 48); 23 Jan 2019 10:11:26 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-DqvXdZezjx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03262.txt.bz2
Content-length: 1722

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

--- Comment #35 from Chris Elrod <elrodc at gmail dot com> ---
> rsqrt:
> .LFB12:
>         .cfi_startproc
>         vrsqrt28ps      (%rsi), %zmm0
>         vmovups %zmm0, (%rdi)
>         vzeroupper
>         ret
> 
> (huh?  isn't there a NR step missing?)
> 


I assume because vrsqrt28ps is much more accurate than vrsqrt14ps, it wasn't
considered necessary. Unfortunately, march=skylake-avx512 does not have
-mavx512er, and therefore should use the less accurate vrsqrt14ps + NR step.

I think vrsqrt14pd/s are -mavx512f or -mavx512vl

> Without -mavx512er, we do not have an expander for rsqrtv16sf2, and without that I don't know how the machinery can guess how to use rsqrt (there are probably ways).

Looking at the asm from only r[i] = sqrtf(a[i]):

        vmovups (%rsi), %zmm1
        vxorps  %xmm0, %xmm0, %xmm0
        vcmpps  $4, %zmm1, %zmm0, %k1
        vrsqrt14ps      %zmm1, %zmm0{%k1}{z}
        vmulps  %zmm1, %zmm0, %zmm1
        vmulps  %zmm0, %zmm1, %zmm0
        vmulps  .LC1(%rip), %zmm1, %zmm1
        vaddps  .LC0(%rip), %zmm0, %zmm0
        vmulps  %zmm1, %zmm0, %zmm0
        vmovups %zmm0, (%rdi)

vs the asm from only r[i] = 1 /a[i]:

        vmovups (%rsi), %zmm1
        vrcp14ps        %zmm1, %zmm0
        vmulps  %zmm1, %zmm0, %zmm1
        vmulps  %zmm1, %zmm0, %zmm1
        vaddps  %zmm0, %zmm0, %zmm0
        vsubps  %zmm1, %zmm0, %zmm0
        vmovups %zmm0, (%rdi)

it looks like the expander is there for sqrt, and for inverse, and we're just
getting both one after the other. So it does look like I could benchmark which
one is slower than the regular instruction on my platform, if that would be
useful.
>From gcc-bugs-return-630454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:25:39 2019
Return-Path: <gcc-bugs-return-630454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113744 invoked by alias); 23 Jan 2019 10:25:19 -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 95966 invoked by uid 48); 23 Jan 2019 10:25:13 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-1VC4NMZtVY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03263.txt.bz2
Content-length: 1561

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

--- Comment #24 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Steve Ellcey from comment #21)
> Successfully matched this instruction:
> (set (zero_extract:SI (reg/i:SI 0 x0)
>         (const_int 8 [0x8])
>         (const_int 12 [0xc]))
>     (zero_extend:SI (reg:QI 1 x1 [ y ])))
> allowing combination of insns 8, 9 and 15
> original costs 4 + 4 + 4 = 12
> replacement cost 4
> deferring deletion of insn with uid = 9.

zero_extract on a destination register is a read-modify write operation, which
means that we'll almost never generate this through combine now as it would
require the same pseudo register as both a source and a destination in the
insns to be combined.  In the past we'd sometimes see this in real code due to
hard registers appearing to combine and giving it the opportunity to create the
pattern.

Perhaps its time for a new way of expressing bit-field insert operations in the
compiler so that the entire operation is expressed on the right hand side of
the set and the entire result can then be assigned to a pseudo (the or-and-and
mess with constants is a nightmare to match, and a nightmare to emit the final
instructions).  Register allocation can then tie that to an input register if
required.  This would be a much better match for RISC based ISAs with bitfield
insert operations, but probably wouldn't be much use on CISC architectures that
can do bit-field inserts directly to memory.

But clearly that's not a gcc-9 type change.
>From gcc-bugs-return-630455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:27:02 2019
Return-Path: <gcc-bugs-return-630455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19565 invoked by alias); 23 Jan 2019 10:27:01 -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 8446 invoked by uid 48); 23 Jan 2019 10:26:57 -0000
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89009] New: Miscompilation (missing function call) with -fvisibility=hidden -fpic -O2 -fno-inline
Date: Wed, 23 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sbergman at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89009-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: 2019-01/txt/msg03264.txt.bz2
Content-length: 1346

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

            Bug ID: 89009
           Summary: Miscompilation (missing function call) with
                    -fvisibility=hidden -fpic -O2 -fno-inline
           Product: gcc
           Version: 8.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sbergman at redhat dot com
  Target Milestone: ---

On Linux x86-64 with at least with GCC 8.2.1 (gcc-8.2.1-6.fc29.x86_64) and
recent trunk towards GCC 9, compiling

> $ cat test.cc
> void f1();
> struct S1 { static void f2(); };
> struct __attribute__ ((visibility("default"))) S2: S1 { static void f2(); };
> struct S3: S1 { static void f2(); };
> struct S4: S3 { static void f2(); };
> void S2::f2() { S1::f2(); }
> void S3::f2() { S1::f2(); }
> void S4::f2() {
>     f1();
>     S3::f2(); // MISSING
> }
> 
> $ g++ -fvisibility=hidden -fpic -O2 -fno-inline -S test.cc

causes the call to S3::f2 to be missing from the code generated for S4::f2:

>         .globl  _ZN2S42f2Ev
>         .hidden _ZN2S42f2Ev
>         .type   _ZN2S42f2Ev, @function
> _ZN2S42f2Ev:
> .LFB2:
>         .cfi_startproc
>         jmp     _Z2f1v@PLT
>         .cfi_endproc
> .LFE2:
>         .size   _ZN2S42f2Ev, .-_ZN2S42f2Ev
>From gcc-bugs-return-630457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:42:53 2019
Return-Path: <gcc-bugs-return-630457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71471 invoked by alias); 23 Jan 2019 10:42:53 -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 59346 invoked by uid 48); 23 Jan 2019 10:42:49 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89010] Update URLs in libsanitizer/README.gcc
Date: Wed, 23 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
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: attachments.created
Message-ID: <bug-89010-4-v0g2vnMgxT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89010-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: 2019-01/txt/msg03266.txt.bz2
Content-length: 350

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

--- Comment #1 from Jonny Grant <jg at jguk dot org> ---
Created attachment 45505
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45505&action=edit
README.gcc.patch

2019-01-23  Jonny Grant  <jg@jguk.org>

        PR 89010
        * libsanitizer/README.gcc: Update to current https URLs
>From gcc-bugs-return-630456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:42:06 2019
Return-Path: <gcc-bugs-return-630456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57151 invoked by alias); 23 Jan 2019 10:42: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 43716 invoked by uid 48); 23 Jan 2019 10:41:59 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89010] New: Update URLs in libsanitizer/README.gcc
Date: Wed, 23 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-89010-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: 2019-01/txt/msg03265.txt.bz2
Content-length: 688

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

            Bug ID: 89010
           Summary: Update URLs in libsanitizer/README.gcc
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jg at jguk dot org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

trunk/libsanitizer/README.gcc
URLs are out of date and weren't https.
Attaching patch and ChangeLog.
>From gcc-bugs-return-630459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:50:00 2019
Return-Path: <gcc-bugs-return-630459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46909 invoked by alias); 23 Jan 2019 10:49:59 -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 46813 invoked by uid 48); 23 Jan 2019 10:49:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-BbDUu6Lwaa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03268.txt.bz2
Content-length: 400

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

--- Comment #25 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We have BIT_INSERT_EXPR on GIMPLE, which in the end is a quarternary operation
previous value, value to insert, bit position and bit size (the last one is
implicit in this GIMPLE op), so you're arguing we should have a similar
expression in RTL, right?  Say BIT_INSERT or INSV?
>From gcc-bugs-return-630458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:49:31 2019
Return-Path: <gcc-bugs-return-630458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23538 invoked by alias); 23 Jan 2019 10:49:30 -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 14121 invoked by uid 48); 23 Jan 2019 10:49:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-b5iS4Z1mc5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03267.txt.bz2
Content-length: 351

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

--- Comment #8 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
(In reply to Martin LiÅ¡ka from comment #7)
> Created attachment 45504 [details]
> Untested patch candidate
> 
> @Martin: Can you please take a look at the patch?

The patch survives regression tests and bootstraps fine.
>From gcc-bugs-return-630460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:52:06 2019
Return-Path: <gcc-bugs-return-630460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16520 invoked by alias); 23 Jan 2019 10:52:05 -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 3885 invoked by uid 48); 23 Jan 2019 10:52:01 -0000
From: "moussu.robin at pm dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Wed, 23 Jan 2019 10:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: moussu.robin at pm dot me
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88994-4-q3Z2zeoN5q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03269.txt.bz2
Content-length: 343

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

--- Comment #4 from Robin <moussu.robin at pm dot me> ---
Perfect! How do I test your patch. If I update my git clone of gcc (gcov is in
gcc repo, isn't it?), it should already be in it, or do I need to wait a few
days?
I guess I can also apply the patch itself on my repo then rebuild.
>From gcc-bugs-return-630461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:54:16 2019
Return-Path: <gcc-bugs-return-630461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79893 invoked by alias); 23 Jan 2019 10:54:15 -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 67458 invoked by uid 48); 23 Jan 2019 10:54:12 -0000
From: "ahangauer at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89011] New: member function pointer template argument with initialization by constant generates ICE
Date: Wed, 23 Jan 2019 10:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ahangauer at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89011-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: 2019-01/txt/msg03270.txt.bz2
Content-length: 2487

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

            Bug ID: 89011
           Summary: member function pointer template argument with
                    initialization by constant generates ICE
           Product: gcc
           Version: 7.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ahangauer at gmx dot net
  Target Milestone: ---

The following code 

template <class X, bool (X::*fcn)(int param)=0 >
struct test   {
        int v;
};

struct dummy {
        bool fcn(int);
};
using TT = test<dummy, &dummy::fcn>;    // works
using TT = test<dummy, 0>;                              // generates ICE
using TT = test<dummy>;                                 // generates ICE


generates an ICE on my gcc:

test_bug.cpp:12:25: internal compiler error: in instantiate_type, at
cp/class.c:8504
 using TT = test<dummy, 0>;
                         ^
libbacktrace could not find executable to open
Please submit a full bug report.

This is the gcc -v output 

Using built-in specs.
COLLECT_GCC=C:\msys64\mingw64\bin\gcc.exe
COLLECT_LTO_WRAPPER=C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/7.3.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../gcc-7.3.0/configure --prefix=/mingw64
--with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32
--host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32
--with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include
--libexecdir=/mingw64/lib --enable-bootstrap --with-arch=x86-64
--with-tune=generic --enable-languages=c,lto,c++,objc,obj-c++,fortran,ada
--enable-shared --enable-static --enable-libatomic --enable-threads=posix
--enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-time=yes
--enable-libstdcxx-filesystem-ts=yes --disable-libstdcxx-pch
--disable-libstdcxx-debug --disable-isl-version-check --enable-lto
--enable-libgomp --disable-multilib --enable-checking=release --disable-rpath
--disable-win32-registry --disable-nls --disable-werror --disable-symvers
--with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64
--with-mpc=/mingw64 --with-isl=/mingw64 --with-pkgversion='Rev2, Built by MSYS2
project' --with-bugurl=https://sourceforge.net/projects/msys2 --with-gnu-as
--with-gnu-ld
Thread model: posix
gcc version 7.3.0 (Rev2, Built by MSYS2 project)
>From gcc-bugs-return-630462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 10:57:31 2019
Return-Path: <gcc-bugs-return-630462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120507 invoked by alias); 23 Jan 2019 10:57:30 -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 102821 invoked by uid 48); 23 Jan 2019 10:57:25 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 10:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-RBDQkUVXpp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03271.txt.bz2
Content-length: 619

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

--- Comment #26 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #25)
> We have BIT_INSERT_EXPR on GIMPLE, which in the end is a quarternary
> operation previous value, value to insert, bit position and bit size (the
> last one is implicit in this GIMPLE op), so you're arguing we should have a
> similar expression in RTL, right?  Say BIT_INSERT or INSV?

Yes, something like that.  I know new RTL codes can be problematic, but clearly
zero_extract on a SET_DEST isn't cutting it any more, if it ever really did.
>From gcc-bugs-return-630463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 11:04:12 2019
Return-Path: <gcc-bugs-return-630463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109463 invoked by alias); 23 Jan 2019 11:04:11 -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 94862 invoked by uid 48); 23 Jan 2019 11:04:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89010] Update URLs in libsanitizer/README.gcc
Date: Wed, 23 Jan 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-89010-4-DooWpx1qan@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89010-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: 2019-01/txt/msg03272.txt.bz2
Content-length: 554

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
     Ever confirmed|0                           |1

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
The patch looks fine to me. Will you send the patch to the GCC mailing list?
>From gcc-bugs-return-630464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 11:22:26 2019
Return-Path: <gcc-bugs-return-630464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123680 invoked by alias); 23 Jan 2019 11:22:25 -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 122407 invoked by uid 48); 23 Jan 2019 11:22:18 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88980] [9 regression] segfault on allocatable string member assignment
Date: Wed, 23 Jan 2019 11:22: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc cf_known_to_work blocked everconfirmed cf_known_to_fail
Message-ID: <bug-88980-4-xWyGvakwRA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88980-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: 2019-01/txt/msg03273.txt.bz2
Content-length: 1108

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-23
                 CC|                            |pault at gcc dot gnu.org
      Known to work|                            |7.4.0, 8.2.0
             Blocks|                            |68241
     Ever confirmed|0                           |1
      Known to fail|                            |9.0

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> This code gives seg fault in 9.0.0 20181010 and 9.0.0 20190103, OK in 8.2.1:

Reduced range: r264722 (2018-09-30, OK) and r264810 (2018-10-03, serrault),
likely r264724 (pr70752, pr72709).


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68241
[Bug 68241] [meta-bug] [F03] Deferred-length character
>From gcc-bugs-return-630465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 11:31:12 2019
Return-Path: <gcc-bugs-return-630465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57289 invoked by alias); 23 Jan 2019 11:31: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 50711 invoked by uid 48); 23 Jan 2019 11:31:00 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89010] Update URLs in libsanitizer/README.gcc
Date: Wed, 23 Jan 2019 11:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot 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:
Message-ID: <bug-89010-4-WvsCPzhdzW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89010-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: 2019-01/txt/msg03274.txt.bz2
Content-length: 247

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

--- Comment #3 from Jonny Grant <jg at jguk dot org> ---
(In reply to Martin LiÅ¡ka from comment #2)
> The patch looks fine to me. Will you send the patch to the GCC mailing list?

Sent!
>From gcc-bugs-return-630466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 11:33:38 2019
Return-Path: <gcc-bugs-return-630466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118680 invoked by alias); 23 Jan 2019 11:33:37 -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 108179 invoked by uid 48); 23 Jan 2019 11:33:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Wed, 23 Jan 2019 11:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88994-4-Vyxsi2XPdx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03275.txt.bz2
Content-length: 435

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

--- Comment #5 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
(In reply to Robin from comment #4)
> Perfect! How do I test your patch. If I update my git clone of gcc (gcov is
> in gcc repo, isn't it?), it should already be in it, or do I need to wait a
> few days?
> I guess I can also apply the patch itself on my repo then rebuild.

I'll install the patch tomorrow.
>From gcc-bugs-return-630467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 11:37:56 2019
Return-Path: <gcc-bugs-return-630467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10320 invoked by alias); 23 Jan 2019 11:37:55 -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 8938 invoked by uid 48); 23 Jan 2019 11:37:49 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88900] [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
Date: Wed, 23 Jan 2019 11:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88900-4-eO8QJmolrf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88900-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: 2019-01/txt/msg03276.txt.bz2
Content-length: 1315

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

--- Comment #6 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
I first isolated minimal test-case for which I can see the miscompilation of
the benchmark compiler:

$ cat scilab.c
int a, b, c, d;
void e() { a = (d >= c ? d : c) - 1 + b; }

$ bash -x ./reduce-ice.sh scilab.c 
+ TC1=scilab.c
+
/home/marxin/Programming/cpu2017/benchspec/CPU/502.gcc_r/build/build_peak_gcc7-m64.0000/cpugcc_r
scilab.c -fpic -o 1.s
+ test 0 = 0
+ /tmp/502gcc/build/build_peak_gcc7-m64.0000/cpugcc_r scilab.c -fpic -o 2.s
+ test 0 = 0
+ diff -u 1.s 2.s
--- 1.s 2019-01-23 12:36:20.815829891 +0100
+++ 2.s 2019-01-23 12:36:20.831830396 +0100
@@ -4,26 +4,23 @@
 .globl e
        .type   e, @function
 e:
+       call    __i686.get_pc_thunk.cx
+       addl    $_GLOBAL_OFFSET_TABLE_, %ecx
        pushl   %ebp
        movl    %esp, %ebp
-       pushl   %ebx
-       call    __i686.get_pc_thunk.bx
-       addl    $_GLOBAL_OFFSET_TABLE_, %ebx
-       movl    b@GOT(%ebx), %eax
-       movl    (%eax), %ecx
-       movl    d@GOT(%ebx), %eax
-       subl    $1, %ecx
+       movl    d@GOT(%ecx), %eax
        movl    (%eax), %edx
-       movl    c@GOT(%ebx), %eax
+       movl    c@GOT(%ecx), %eax
...

Not I'm going to find a minimal set of LTO object files needed.
>From gcc-bugs-return-630468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 11:41:45 2019
Return-Path: <gcc-bugs-return-630468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9802 invoked by alias); 23 Jan 2019 11:41:43 -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 124279 invoked by uid 55); 23 Jan 2019 11:41:38 -0000
From: "moussu.robin at pm dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Wed, 23 Jan 2019 11:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: moussu.robin at pm dot me
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88994-4-atD34gLyjJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03277.txt.bz2
Content-length: 787

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

--- Comment #6 from Robin <moussu.robin at pm dot me> ---
Ok, thx

EnvoyÃ© depuis ProtonMail mobile

-------- Message d'origine --------
On 23 janv. 2019 Ã  12:33, marxin at gcc dot gnu.org a Ã©crit :

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88994
>
> --- Comment #5 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
> (In reply to Robin from comment #4)
>> Perfect! How do I test your patch. If I update my git clone of gcc (gcov is
>> in gcc repo, isn't it?), it should already be in it, or do I need to wait a
>> few days?
>> I guess I can also apply the patch itself on my repo then rebuild.
>
> I'll install the patch tomorrow.
>
> --
> You are receiving this mail because:
> You reported the bug.
>From gcc-bugs-return-630469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:01:35 2019
Return-Path: <gcc-bugs-return-630469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38964 invoked by alias); 23 Jan 2019 12:01:19 -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 17575 invoked by uid 48); 23 Jan 2019 12:01:09 -0000
From: "antony at cosmologist dot info" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87566] ICE with class(*) and select
Date: Wed, 23 Jan 2019 12:01: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: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antony at cosmologist dot info
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87566-4-1B2uIO71Vt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87566-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87566-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: 2019-01/txt/msg03278.txt.bz2
Content-length: 449

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

--- Comment #10 from Antony Lewis <antony at cosmologist dot info> ---
In the latest 9.0 trunk I still see what looks like a similar ICE error (though
I have not tried to isolate it again). See

https://travis-ci.org/cmbant/forutils/builds/483365115

when running test script in https://github.com/cmbant/forutils/tree/gcc_bug1 .
(code is reported invalid in gcc6, but SEG faults in 7,8,9).
>From gcc-bugs-return-630470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:03:49 2019
Return-Path: <gcc-bugs-return-630470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118114 invoked by alias); 23 Jan 2019 12:03:48 -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 108147 invoked by uid 48); 23 Jan 2019 12:03:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 12:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-89008-4-hSmz1h0EPT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03279.txt.bz2
Content-length: 1322

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |6.4.0, 9.0
           Keywords|                            |needs-bisection, wrong-code
   Last reconfirmed|                            |2019-01-23
                 CC|                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1
            Summary|O2 and O1 results differ    |[7/8 Regression] O2 and O1
                   |for simple test             |results differ for simple
                   |                            |test
   Target Milestone|---                         |7.5
      Known to fail|                            |7.4.0, 8.2.0

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  Seems to work on trunk, disabling SLSR fixes it.  We end up with

f ()
{
  <bb 2> [local count: 14598063]:
  b = 0;
  c = 4;
  e = 6;
  d = 6;
  a = 4294967292;
  return 0;

so I guess a fix needs backporting.  Martin, can you bisect the fix?
>From gcc-bugs-return-630471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:10:18 2019
Return-Path: <gcc-bugs-return-630471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110999 invoked by alias); 23 Jan 2019 12:10:17 -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 99686 invoked by uid 48); 23 Jan 2019 12:10:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 12:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-89008-4-JW60b4GHSu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03280.txt.bz2
Content-length: 951

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wschmidt at gcc dot gnu.org

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Eventually the issue also just became latent.  SLSR does

Replacing: _7 = _12 * 83886080;
With: _7 = _12;

Replacing: _19 = _12 * 2;
With: _19 = _2;

where the latter is bogus replacing 0 with 4.  Eventually SLSR is confused by

  _12 = b_lsm.9_34 * 0;

being present in the IL, not sure.  IL before SLSR:

  _12 = b_lsm.9_34 * 0;
...
  _2 = _12 + 4;
...
  _19 = _12 * 2;
  _6 = -_19;
  g_21 = (long unsigned int) _6;
  a = g_21;

possibly checks some multiple-of which breaks down with zero.

On trunk the * 0 is gone (possibly the "fix").
>From gcc-bugs-return-630472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:13:10 2019
Return-Path: <gcc-bugs-return-630472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128989 invoked by alias); 23 Jan 2019 12:13:09 -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 26630 invoked by uid 48); 23 Jan 2019 12:12:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 12:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89008-4-vLaovIsRu3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03281.txt.bz2
Content-length: 173

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

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Started with r236440 and was fixed with r263875.
>From gcc-bugs-return-630473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:25:23 2019
Return-Path: <gcc-bugs-return-630473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6664 invoked by alias); 23 Jan 2019 12:25:15 -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 99379 invoked by uid 48); 23 Jan 2019 12:24:22 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 12:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89008-4-vyh2wa1BAB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03282.txt.bz2
Content-length: 1032

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Martin LiÅ¡ka from comment #3)
> Started with r236440 and was fixed with r263875.

Thanks Martin - this means both the * 0 added by reassoc and the SLSR issue
are latent.

Found * 0, removing all other ops
Width = 1 was chosen for reassociation
Transforming _12 = _10 * 83886080;
 into _12 = b_lsm.9_34 * 0;

GIMPLE testcase that shows the above on trunk:

unsigned long a;
unsigned b;
long int __GIMPLE (startwith("reassoc"))
f ()
{
  unsigned int _4;
  unsigned int _6;
  unsigned int _10;
  unsigned int _12;
  unsigned int _19;
  unsigned int _33;
  unsigned int _36;
  unsigned long g_21;
  unsigned int b_lsm9_34;

  bb_2:
  b_lsm9_34 = b;
  _36 = b_lsm9_34 * 83886080u;
  _33 = _36 * 83886080u;
  _4 = _33 * 83886080u;
  _10 = _4 * 83886080u;
  _12 = _10 * 83886080u;
  _19 = _12 * 2u;
  _6 = -_19;
  g_21 = (long unsigned int) _6;
  a = g_21;
  return 0l;

}
>From gcc-bugs-return-630474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:31:36 2019
Return-Path: <gcc-bugs-return-630474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54014 invoked by alias); 23 Jan 2019 12:31:36 -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 44058 invoked by uid 48); 23 Jan 2019 12:31:31 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86946] ICE: canonical types differ for identical types
Date: Wed, 23 Jan 2019 12:31: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
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:
Message-ID: <bug-86946-4-OtkgJ9B3Kz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86946-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86946-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: 2019-01/txt/msg03283.txt.bz2
Content-length: 217

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

--- Comment #5 from David Binderman <dcb314 at hotmail dot com> ---
This bug has been hanging around for months now. 

Should it be marked as a 9.0 regression ?
>From gcc-bugs-return-630475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:34:14 2019
Return-Path: <gcc-bugs-return-630475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118390 invoked by alias); 23 Jan 2019 12:34:13 -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 105418 invoked by uid 48); 23 Jan 2019 12:34:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/89009] [7/8/9 Regression] Miscompilation (missing function call) with -fvisibility=hidden -fpic -O2 -fno-inline
Date: Wed, 23 Jan 2019 12:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on component cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-89009-4-QQfE8vNuZX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89009-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: 2019-01/txt/msg03284.txt.bz2
Content-length: 1413

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
             Status|UNCONFIRMED                 |NEW
      Known to work|                            |6.5.0
           Keywords|                            |wrong-code
   Last reconfirmed|                            |2019-01-23
          Component|c++                         |ipa
                 CC|                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1
            Summary|Miscompilation (missing     |[7/8/9 Regression]
                   |function call) with         |Miscompilation (missing
                   |-fvisibility=hidden -fpic   |function call) with
                   |-O2 -fno-inline             |-fvisibility=hidden -fpic
                   |                            |-O2 -fno-inline
   Target Milestone|---                         |7.5
      Known to fail|                            |7.4.0, 8.2.1, 9.0

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Oddly with just -O2 -fno-inline we call S2::f2 () (it got ICFed with S3::f2
it seems).

Disabling ICF also fixes the omission of the call for -fpic
-fvisibility=hidden.
>From gcc-bugs-return-630476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:43:14 2019
Return-Path: <gcc-bugs-return-630476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11567 invoked by alias); 23 Jan 2019 12:43:12 -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 128792 invoked by uid 48); 23 Jan 2019 12:43:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 12:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-89008-4-aYqXoU8qrG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03285.txt.bz2
Content-length: 391

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45506
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45506&action=edit
patch for the * 0 issue in reassoc

I am testing a mitigation (and missed optimization fix) in reassoc.  Bill, can
you look into the SLSR issue which is still latent?
>From gcc-bugs-return-630477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:43:48 2019
Return-Path: <gcc-bugs-return-630477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92075 invoked by alias); 23 Jan 2019 12:43:47 -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 78355 invoked by uid 48); 23 Jan 2019 12:43:44 -0000
From: "ahangauer at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89011] member function pointer template argument with initialization by constant generates ICE
Date: Wed, 23 Jan 2019 12:43: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: 7.3.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ahangauer at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89011-4-0hGQmMjhzq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89011-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89011-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: 2019-01/txt/msg03286.txt.bz2
Content-length: 609

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

--- Comment #1 from Andreas Hangauer <ahangauer at gmx dot net> ---
I just found out that using nullptr it *does* work. So it is the initialization
by integer zero that does not work.

#include <cstddef>

template <class X, bool (X::*fcn)(int param)=0 >
struct test   {
        int v;
};

struct dummy {
        bool fcn(int);
};

using TT = test<dummy, &dummy::fcn>;    // works
using TT2 = test<dummy, nullptr>;       // works
using TT3 = test<dummy, 0>;             // generates ICE
using TT4 = test<dummy>;                // generates ICE
>From gcc-bugs-return-630478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 12:51:57 2019
Return-Path: <gcc-bugs-return-630478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67104 invoked by alias); 23 Jan 2019 12:51:56 -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 55234 invoked by uid 48); 23 Jan 2019 12:51:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88900] [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
Date: Wed, 23 Jan 2019 12:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88900-4-q51mVn1lnH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88900-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: 2019-01/txt/msg03287.txt.bz2
Content-length: 242

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

--- Comment #7 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Using -flto only for tree-ssa-reassoc.o produces the miscompiled GCC (other
files are takes from -O2 -fno-lto build).
>From gcc-bugs-return-630479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:04:46 2019
Return-Path: <gcc-bugs-return-630479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79258 invoked by alias); 23 Jan 2019 13:04:45 -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 70548 invoked by uid 48); 23 Jan 2019 13:04:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88900] [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
Date: Wed, 23 Jan 2019 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88900-4-6mxWGhh2Ol@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88900-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: 2019-01/txt/msg03288.txt.bz2
Content-length: 570

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|needs-reduction             |

--- Comment #8 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Ok, compiled binary differs in spec_qsort. That's a known problem and we should
use -fno-strict-aliasing. As mentioned here:
https://www.spec.org/cpu2017/Docs/benchmarks/502.gcc_r.html

I'm testing that..
>From gcc-bugs-return-630480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:07:52 2019
Return-Path: <gcc-bugs-return-630480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23125 invoked by alias); 23 Jan 2019 13:07:51 -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 18597 invoked by uid 48); 23 Jan 2019 13:07:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/89009] [7/8/9 Regression] Miscompilation (missing function call) with -fvisibility=hidden -fpic -O2 -fno-inline
Date: Wed, 23 Jan 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-89009-4-0ciO7JzpXu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89009-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: 2019-01/txt/msg03289.txt.bz2
Content-length: 476

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Let me take a look..
>From gcc-bugs-return-630482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:16:13 2019
Return-Path: <gcc-bugs-return-630482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38965 invoked by alias); 23 Jan 2019 13:16:12 -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 36049 invoked by uid 48); 23 Jan 2019 13:16:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Wed, 23 Jan 2019 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: marxin 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: bug_status resolution
Message-ID: <bug-26163-4-RZn0epSQJX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-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: 2019-01/txt/msg03291.txt.bz2
Content-length: 498

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 88900, which changed state.

Bug 88900 Summary: [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88900

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID
>From gcc-bugs-return-630481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:16:09 2019
Return-Path: <gcc-bugs-return-630481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38269 invoked by alias); 23 Jan 2019 13:16:08 -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 30176 invoked by uid 48); 23 Jan 2019 13:16:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88900] [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
Date: Wed, 23 Jan 2019 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88900-4-uHioL4QqK0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88900-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: 2019-01/txt/msg03290.txt.bz2
Content-length: 461

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

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID

--- Comment #9 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Yes, -fno-strict-aliasing works!
>From gcc-bugs-return-630483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:18:57 2019
Return-Path: <gcc-bugs-return-630483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85912 invoked by alias); 23 Jan 2019 13:18:57 -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 71759 invoked by uid 55); 23 Jan 2019 13:18:53 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88900] [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
Date: Wed, 23 Jan 2019 13:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88900-4-MjCIZJtKCY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88900-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: 2019-01/txt/msg03292.txt.bz2
Content-length: 767

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

--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 23 Jan 2019, marxin at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88900
> 
> Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|ASSIGNED                    |RESOLVED
>          Resolution|---                         |INVALID
> 
> --- Comment #9 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
> Yes, -fno-strict-aliasing works!

You can also try the specifc source fix to spec_qsort which IIRC
I attached somewhere...
>From gcc-bugs-return-630484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:19:28 2019
Return-Path: <gcc-bugs-return-630484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44117 invoked by alias); 23 Jan 2019 13:19:25 -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 34407 invoked by uid 55); 23 Jan 2019 13:19:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89010] Update URLs in libsanitizer/README.gcc
Date: Wed, 23 Jan 2019 13:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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:
Message-ID: <bug-89010-4-qPvBybkDQv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89010-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: 2019-01/txt/msg03293.txt.bz2
Content-length: 429

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 23 13:18:50 2019
New Revision: 268183

URL: https://gcc.gnu.org/viewcvs?rev=268183&root=gcc&view=rev
Log:
        PR sanitizer/89010
        * libsanitizer/README.gcc: Update to current https URLs.

Modified:
    trunk/libsanitizer/ChangeLog
    trunk/libsanitizer/README.gcc
>From gcc-bugs-return-630485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:34:31 2019
Return-Path: <gcc-bugs-return-630485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30810 invoked by alias); 23 Jan 2019 13:34:31 -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 26741 invoked by uid 48); 23 Jan 2019 13:34:27 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87214] [9 Regression] r263772 miscompiled 520.omnetpp_r in SPEC CPU 2017
Date: Wed, 23 Jan 2019 13:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87214-4-yfWfHct6bQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87214-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: 2019-01/txt/msg03294.txt.bz2
Content-length: 455

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
Adding -fno-strict-aliasing fixes the issue.
>From gcc-bugs-return-630486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:34:33 2019
Return-Path: <gcc-bugs-return-630486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31667 invoked by alias); 23 Jan 2019 13:34:33 -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 28918 invoked by uid 48); 23 Jan 2019 13:34:29 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Wed, 23 Jan 2019 13:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
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: bug_status resolution
Message-ID: <bug-26163-4-Y7OrXjuF8X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-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: 2019-01/txt/msg03295.txt.bz2
Content-length: 495

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 87214, which changed state.

Bug 87214 Summary: [9 Regression] r263772 miscompiled 520.omnetpp_r in SPEC CPU 2017
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87214

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID
>From gcc-bugs-return-630487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:42:14 2019
Return-Path: <gcc-bugs-return-630487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45903 invoked by alias); 23 Jan 2019 13:42:12 -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 37162 invoked by uid 48); 23 Jan 2019 13:42:09 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88850] [9 Regression] Hard register coming out of expand causing reload to fail.
Date: Wed, 23 Jan 2019 13:42: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88850-4-iQCJ94L3dL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88850-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: 2019-01/txt/msg03296.txt.bz2
Content-length: 292

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

--- Comment #7 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Thanks for the information  Vladimir,

I wasn't aware of this special treatment of cost 2. Changing the cost does
indeed fix the ICE.

Working on a sensible patch now.
>From gcc-bugs-return-630488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:43:16 2019
Return-Path: <gcc-bugs-return-630488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111613 invoked by alias); 23 Jan 2019 13:43:15 -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 98526 invoked by uid 48); 23 Jan 2019 13:43:11 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88560] [9 Regression] armv8_2-fp16-move-1.c and related regressions after r266385
Date: Wed, 23 Jan 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88560-4-Ri7RzQlnDS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88560-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: 2019-01/txt/msg03297.txt.bz2
Content-length: 505

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

Tamar Christina <tnfchris at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tnfchris at gcc dot gnu.org

--- Comment #10 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Thanks for the patch Vladimir!

I've started a validation of the patch, will let you know as soon as it
finishes.
>From gcc-bugs-return-630489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:50:11 2019
Return-Path: <gcc-bugs-return-630489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114569 invoked by alias); 23 Jan 2019 13:50: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 114489 invoked by uid 48); 23 Jan 2019 13:50:06 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 13:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-hzeYuJHAAN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03298.txt.bz2
Content-length: 1430

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

--- Comment #36 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Biener from comment #34)
> GCC definitely fails to see the FMA use as opportunity in
> ix86_emit_swsqrtsf, the a == 0 checking is because of the missing
> expander w/o avx512er where we could still use the NR sequence
> with the other instruction.  HJ?

Like this?

diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
index e0d7c74fcec..0bbe3772ab7 100644
--- a/gcc/config/i386/i386.c
+++ b/gcc/config/i386/i386.c
@@ -44855,14 +44855,22 @@ void ix86_emit_swsqrtsf (rtx res, rtx a, machine_mode
mode, bool recip)
        }
     }

+  mthree = force_reg (mode, mthree);
+
   /* e0 = x0 * a */
   emit_insn (gen_rtx_SET (e0, gen_rtx_MULT (mode, x0, a)));
-  /* e1 = e0 * x0 */
-  emit_insn (gen_rtx_SET (e1, gen_rtx_MULT (mode, e0, x0)));

-  /* e2 = e1 - 3. */
-  mthree = force_reg (mode, mthree);
-  emit_insn (gen_rtx_SET (e2, gen_rtx_PLUS (mode, e1, mthree)));
+  if (TARGET_FMA || TARGET_AVX512F)
+    emit_insn (gen_rtx_SET (e2,
+                           gen_rtx_FMA (mode, e0, x0, mthree)));
+  else
+    {
+      /* e1 = e0 * x0 */
+      emit_insn (gen_rtx_SET (e1, gen_rtx_MULT (mode, e0, x0)));
+
+      /* e2 = e1 - 3. */
+      emit_insn (gen_rtx_SET (e2, gen_rtx_PLUS (mode, e1, mthree)));
+    }

   mhalf = force_reg (mode, mhalf);
   if (recip)
>From gcc-bugs-return-630490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:55:01 2019
Return-Path: <gcc-bugs-return-630490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36456 invoked by alias); 23 Jan 2019 13:55:01 -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 22676 invoked by uid 55); 23 Jan 2019 13:54:56 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87893] [9 Regression] ICE in gimplify_expr, at gimplify.c:12557 on arm-linux-gnueabi
Date: Wed, 23 Jan 2019 13:55: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87893-4-xE2Xzyj6Vs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87893-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: 2019-01/txt/msg03299.txt.bz2
Content-length: 664

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

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Wed Jan 23 13:54:23 2019
New Revision: 268185

URL: https://gcc.gnu.org/viewcvs?rev=268185&root=gcc&view=rev
Log:
        PR c++/87893 - constexpr ctor ICE on ARM.

        PR c++/88293 - ICE with comma expression.
        * constexpr.c (initialized_type): Don't shortcut non-void type.
        Handle COMPOUND_EXPR.
        (cxx_eval_outermost_constant_expr): Return early for void type.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-comma1.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/constexpr.c
>From gcc-bugs-return-630493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:55:32 2019
Return-Path: <gcc-bugs-return-630493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85795 invoked by alias); 23 Jan 2019 13:55:30 -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 62254 invoked by uid 48); 23 Jan 2019 13:55:24 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88293] [9 Regression] ICE on C++11 code: in build_target_expr_with_type, at cp/tree.c:793
Date: Wed, 23 Jan 2019 13:55: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88293-4-zUX17yphPM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88293-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88293-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: 2019-01/txt/msg03302.txt.bz2
Content-length: 423

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:55:03 2019
Return-Path: <gcc-bugs-return-630491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37907 invoked by alias); 23 Jan 2019 13:55:03 -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 30188 invoked by uid 55); 23 Jan 2019 13:54:58 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88293] [9 Regression] ICE on C++11 code: in build_target_expr_with_type, at cp/tree.c:793
Date: Wed, 23 Jan 2019 13:55: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88293-4-8DY2A3tXgU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88293-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88293-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: 2019-01/txt/msg03300.txt.bz2
Content-length: 664

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

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Wed Jan 23 13:54:23 2019
New Revision: 268185

URL: https://gcc.gnu.org/viewcvs?rev=268185&root=gcc&view=rev
Log:
        PR c++/87893 - constexpr ctor ICE on ARM.

        PR c++/88293 - ICE with comma expression.
        * constexpr.c (initialized_type): Don't shortcut non-void type.
        Handle COMPOUND_EXPR.
        (cxx_eval_outermost_constant_expr): Return early for void type.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-comma1.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/constexpr.c
>From gcc-bugs-return-630494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:55:58 2019
Return-Path: <gcc-bugs-return-630494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41763 invoked by alias); 23 Jan 2019 13:55:57 -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 29008 invoked by uid 48); 23 Jan 2019 13:55:53 -0000
From: "florian.schornbaum at siemens dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88531] Index data types when targeting AVX-512 vectorization with gather/scatter
Date: Wed, 23 Jan 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: florian.schornbaum at siemens dot com
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:
Message-ID: <bug-88531-4-wzz1x2YOBw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88531-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: 2019-01/txt/msg03303.txt.bz2
Content-length: 290

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

--- Comment #8 from Florian Schornbaum <florian.schornbaum at siemens dot com> ---
They are definitely a good source to ask.
We'll try to get in contact with them and see if we can get help/insight.

Thanks for all your input so far!
>From gcc-bugs-return-630492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:55:04 2019
Return-Path: <gcc-bugs-return-630492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38123 invoked by alias); 23 Jan 2019 13:55: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 32366 invoked by uid 48); 23 Jan 2019 13:54:59 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Wed, 23 Jan 2019 13:55: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-87935-4-ANFbuFlnPm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg03301.txt.bz2
Content-length: 404

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

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING

--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> ---
Please verify that these are all fixed now.
>From gcc-bugs-return-630495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:56:36 2019
Return-Path: <gcc-bugs-return-630495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57884 invoked by alias); 23 Jan 2019 13:56:36 -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 46282 invoked by uid 55); 23 Jan 2019 13:56:32 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 13:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-FNSKNicocm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03304.txt.bz2
Content-length: 1839

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

--- Comment #37 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 23 Jan 2019, hjl.tools at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #36 from H.J. Lu <hjl.tools at gmail dot com> ---
> (In reply to Richard Biener from comment #34)
> > GCC definitely fails to see the FMA use as opportunity in
> > ix86_emit_swsqrtsf, the a == 0 checking is because of the missing
> > expander w/o avx512er where we could still use the NR sequence
> > with the other instruction.  HJ?
> 
> Like this?

Yes.  The lack of an expander for the rqsrt operation is probably
more severe though (causing sqrt + approx recip to appear)

> diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
> index e0d7c74fcec..0bbe3772ab7 100644
> --- a/gcc/config/i386/i386.c
> +++ b/gcc/config/i386/i386.c
> @@ -44855,14 +44855,22 @@ void ix86_emit_swsqrtsf (rtx res, rtx a, machine_mode
> mode, bool recip)
>         }
>      }
> 
> +  mthree = force_reg (mode, mthree);
> +
>    /* e0 = x0 * a */
>    emit_insn (gen_rtx_SET (e0, gen_rtx_MULT (mode, x0, a)));
> -  /* e1 = e0 * x0 */
> -  emit_insn (gen_rtx_SET (e1, gen_rtx_MULT (mode, e0, x0)));
> 
> -  /* e2 = e1 - 3. */
> -  mthree = force_reg (mode, mthree);
> -  emit_insn (gen_rtx_SET (e2, gen_rtx_PLUS (mode, e1, mthree)));
> +  if (TARGET_FMA || TARGET_AVX512F)
> +    emit_insn (gen_rtx_SET (e2,
> +                           gen_rtx_FMA (mode, e0, x0, mthree)));
> +  else
> +    {
> +      /* e1 = e0 * x0 */
> +      emit_insn (gen_rtx_SET (e1, gen_rtx_MULT (mode, e0, x0)));
> +
> +      /* e2 = e1 - 3. */
> +      emit_insn (gen_rtx_SET (e2, gen_rtx_PLUS (mode, e1, mthree)));
> +    }
> 
>    mhalf = force_reg (mode, mhalf);
>    if (recip)
>From gcc-bugs-return-630496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 13:59:39 2019
Return-Path: <gcc-bugs-return-630496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100770 invoked by alias); 23 Jan 2019 13:59: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 89115 invoked by uid 48); 23 Jan 2019 13:59:32 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 13:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-FPVu4BtuGE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03305.txt.bz2
Content-length: 883

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

--- Comment #38 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to rguenther@suse.de from comment #37)
> On Wed, 23 Jan 2019, hjl.tools at gmail dot com wrote:
> 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> > 
> > --- Comment #36 from H.J. Lu <hjl.tools at gmail dot com> ---
> > (In reply to Richard Biener from comment #34)
> > > GCC definitely fails to see the FMA use as opportunity in
> > > ix86_emit_swsqrtsf, the a == 0 checking is because of the missing
> > > expander w/o avx512er where we could still use the NR sequence
> > > with the other instruction.  HJ?
> > 
> > Like this?
> 
> Yes.  The lack of an expander for the rqsrt operation is probably
> more severe though (causing sqrt + approx recip to appear)
> 

Can we use UNSPEC_RSQRT14 here if UNSPEC_RSQRT28 isn't available?
>From gcc-bugs-return-630497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:01:07 2019
Return-Path: <gcc-bugs-return-630497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41771 invoked by alias); 23 Jan 2019 14:01:05 -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 36477 invoked by uid 48); 23 Jan 2019 14:01:01 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Wed, 23 Jan 2019 14:01: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87935-4-KcD2AxbXST@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg03306.txt.bz2
Content-length: 227

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

--- Comment #7 from Christophe Lyon <clyon at gcc dot gnu.org> ---
We still see the same errors.
We post reports for arm on: https://gcc.gnu.org/ml/gcc-testresults/2019-01/
>From gcc-bugs-return-630498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:02:54 2019
Return-Path: <gcc-bugs-return-630498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15924 invoked by alias); 23 Jan 2019 14:02:53 -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 119275 invoked by uid 55); 23 Jan 2019 14:02:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 14:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89008-4-IjskyG2MB2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03307.txt.bz2
Content-length: 667

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jan 23 14:02:13 2019
New Revision: 268186

URL: https://gcc.gnu.org/viewcvs?rev=268186&root=gcc&view=rev
Log:
2019-01-23  Richard Biener  <rguenther@suse.de>

        PR tree-optimization/89008
        * tree-ssa-reassoc.c (eliminate_using_constants): For * 0 do
        not leave another stray operand.

        * gcc.dg/torture/pr89008.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/pr89008.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-ssa-reassoc.c
>From gcc-bugs-return-630500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:05:32 2019
Return-Path: <gcc-bugs-return-630500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16851 invoked by alias); 23 Jan 2019 14:05:32 -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 11690 invoked by uid 55); 23 Jan 2019 14:05:28 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-SMr8XUa1z6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03309.txt.bz2
Content-length: 1613

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

--- Comment #39 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 23 Jan 2019, hjl.tools at gmail dot com wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #38 from H.J. Lu <hjl.tools at gmail dot com> ---
> (In reply to rguenther@suse.de from comment #37)
> > On Wed, 23 Jan 2019, hjl.tools at gmail dot com wrote:
> > 
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> > > 
> > > --- Comment #36 from H.J. Lu <hjl.tools at gmail dot com> ---
> > > (In reply to Richard Biener from comment #34)
> > > > GCC definitely fails to see the FMA use as opportunity in
> > > > ix86_emit_swsqrtsf, the a == 0 checking is because of the missing
> > > > expander w/o avx512er where we could still use the NR sequence
> > > > with the other instruction.  HJ?
> > > 
> > > Like this?
> > 
> > Yes.  The lack of an expander for the rqsrt operation is probably
> > more severe though (causing sqrt + approx recip to appear)
> > 
> 
> Can we use UNSPEC_RSQRT14 here if UNSPEC_RSQRT28 isn't available?

I think we can but we lack an expander for this.  IIRC for the following
existing expander the RTL is ignored and thus we could simply
replace the TARGET_AVX512ER check with TARGET_AVX512F?

(define_expand "rsqrtv16sf2"
  [(set (match_operand:V16SF 0 "register_operand")
        (unspec:V16SF
          [(match_operand:V16SF 1 "vector_operand")]
          UNSPEC_RSQRT28))]
  "TARGET_SSE_MATH && TARGET_AVX512ER"
{
  ix86_emit_swsqrtsf (operands[0], operands[1], V16SFmode, true);
  DONE;
})
>From gcc-bugs-return-630499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:05:15 2019
Return-Path: <gcc-bugs-return-630499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4007 invoked by alias); 23 Jan 2019 14:05:14 -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 3373 invoked by uid 48); 23 Jan 2019 14:05:09 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87935] [9 regression] new failures on arm since r265788
Date: Wed, 23 Jan 2019 14:05: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87935-4-f1ZVXp4abx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87935-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: 2019-01/txt/msg03308.txt.bz2
Content-length: 246

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

--- Comment #8 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Just noticed your patch
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01367.html
The testers will run during the next hours.
>From gcc-bugs-return-630501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:23:26 2019
Return-Path: <gcc-bugs-return-630501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115309 invoked by alias); 23 Jan 2019 14:23:25 -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 106239 invoked by uid 48); 23 Jan 2019 14:23:22 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88347] ICE in begin_move_insn, at sched-ebb.c:175
Date: Wed, 23 Jan 2019 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm 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: bug_status assigned_to
Message-ID: <bug-88347-4-dKfhQBGafo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88347-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88347-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: 2019-01/txt/msg03310.txt.bz2
Content-length: 586

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
           Assignee|dmalcolm at gcc dot gnu.org        |unassigned at gcc dot gnu.org

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01372.html
(though see the concerns in that thread; un-assigning myself)
>From gcc-bugs-return-630502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:25:15 2019
Return-Path: <gcc-bugs-return-630502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31233 invoked by alias); 23 Jan 2019 14:25:15 -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 16402 invoked by uid 48); 23 Jan 2019 14:25:11 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41023] Inconsistent error locations for wrong interfaces with overloaded operators
Date: Wed, 23 Jan 2019 14:25: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: unknown
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
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:
Message-ID: <bug-41023-4-A0mjN7x8C3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41023-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41023-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: 2019-01/txt/msg03311.txt.bz2
Content-length: 181

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

--- Comment #7 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Has this patch ever been applied and/or reg-tested?
>From gcc-bugs-return-630503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:25:50 2019
Return-Path: <gcc-bugs-return-630503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123900 invoked by alias); 23 Jan 2019 14:25: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 113906 invoked by uid 48); 23 Jan 2019 14:25:45 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-sAkFXSe8yK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03312.txt.bz2
Content-length: 1895

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

--- Comment #40 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to rguenther@suse.de from comment #39)
> > > 
> > > Yes.  The lack of an expander for the rqsrt operation is probably
> > > more severe though (causing sqrt + approx recip to appear)
> > > 
> > 
> > Can we use UNSPEC_RSQRT14 here if UNSPEC_RSQRT28 isn't available?
> 
> I think we can but we lack an expander for this.  IIRC for the following
> existing expander the RTL is ignored and thus we could simply
> replace the TARGET_AVX512ER check with TARGET_AVX512F?
> 
> (define_expand "rsqrtv16sf2"
>   [(set (match_operand:V16SF 0 "register_operand")
>         (unspec:V16SF
>           [(match_operand:V16SF 1 "vector_operand")]
>           UNSPEC_RSQRT28))]
>   "TARGET_SSE_MATH && TARGET_AVX512ER"
> {
>   ix86_emit_swsqrtsf (operands[0], operands[1], V16SFmode, true);
>   DONE;
> })

Like this?

diff --git a/gcc/config/i386/sse.md b/gcc/config/i386/sse.md
index 3af4adc63dd..c9b4750ccc4 100644
--- a/gcc/config/i386/sse.md
+++ b/gcc/config/i386/sse.md
@@ -1969,21 +1969,11 @@
    (set_attr "mode" "<ssescalarmode>")])

 (define_expand "rsqrt<mode>2"
-  [(set (match_operand:VF1_128_256 0 "register_operand")
-  (unspec:VF1_128_256
-    [(match_operand:VF1_128_256 1 "vector_operand")] UNSPEC_RSQRT))]
+  [(set (match_operand:VF_AVX512VL 0 "register_operand")
+  (unspec:VF_AVX512VL
+    [(match_operand:VF_AVX512VL 1 "vector_operand")]
+    UNSPEC_RSQRT))]
   "TARGET_SSE_MATH"
-{
-  ix86_emit_swsqrtsf (operands[0], operands[1], <MODE>mode, true);
-  DONE;
-})
-
-(define_expand "rsqrtv16sf2"
-  [(set (match_operand:V16SF 0 "register_operand")
-  (unspec:V16SF
-    [(match_operand:V16SF 1 "vector_operand")]
-    UNSPEC_RSQRT28))]
-  "TARGET_SSE_MATH && TARGET_AVX512ER"
 {
   ix86_emit_swsqrtsf (operands[0], operands[1], V16SFmode, true);
   DONE;
>From gcc-bugs-return-630504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:29:26 2019
Return-Path: <gcc-bugs-return-630504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113667 invoked by alias); 23 Jan 2019 14:29:25 -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 113547 invoked by uid 48); 23 Jan 2019 14:29:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 14:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-2pe6eKzAWt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03313.txt.bz2
Content-length: 2027

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

--- Comment #27 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, looking at what other targets do on the #c21 testcase, e.g. rs6000 actually
matches what the combiner produces:
Trying 10, 9 -> 11:
   10: r131:SI=r133:DI#0&0xfffffffffff00fff
      REG_DEAD r133:DI
    9: r130:SI=r134:DI#0<<0xc&0xff000
      REG_DEAD r134:DI
   11: r127:SI=r130:SI|r131:SI
      REG_DEAD r131:SI
      REG_DEAD r130:SI
Successfully matched this instruction:
(set (reg:SI 127)
    (ior:SI (and:SI (subreg:SI (reg:DI 133) 0)
            (const_int -1044481 [0xfffffffffff00fff]))
        (and:SI (ashift:SI (subreg:SI (reg:DI 134) 0)
                (const_int 12 [0xc]))
            (const_int 1044480 [0xff000]))))
and we have:
(insn:TI 11 12 17 (set (reg:SI 3 3 [127])
        (ior:SI (and:SI (reg:SI 3 3 [133])
                (const_int -1044481 [0xfffffffffff00fff]))
            (and:SI (ashift:SI (reg:SI 4 4 [134])
                    (const_int 12 [0xc]))
                (const_int 1044480 [0xff000])))) "pr87763.c":3:26 240
{*rotlsi3_insert_2}
     (expr_list:REG_DEAD (reg:SI 4 4 [134])
        (nil)))
until final.
So, any reason why aarch64 can't do that too?
It can be just define_insn_and_split that splits it at the first possible split
occassion.
I see combiner trying:
(set (reg/i:SI 0 x0)
    (ior:SI (and:SI (reg:SI 100)
            (const_int -1044481 [0xfffffffffff00fff]))
        (and:SI (ashift:SI (reg:SI 101)
                (const_int 12 [0xc]))
            (const_int 1044480 [0xff000]))))
Should be easy to verify one of the constants has number of trailing zeros
equal to the shift count, then 1 or more one bits and then all ones above it
and the other constants being negation thereof.
For shift count zero that is obviously a different pattern, and probably for
the swapping of the two ior arguments if combiner doesn't canonicalize them
always one way; you probably need a couple of other patterns, but it all should
be doable in stage4.
>From gcc-bugs-return-630505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:31:27 2019
Return-Path: <gcc-bugs-return-630505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117669 invoked by alias); 23 Jan 2019 14:31:26 -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 117581 invoked by uid 48); 23 Jan 2019 14:31:22 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-muVKMDpuWY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03314.txt.bz2
Content-length: 2093

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

--- Comment #41 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to H.J. Lu from comment #40)
> (In reply to rguenther@suse.de from comment #39)
> > > > 
> > > > Yes.  The lack of an expander for the rqsrt operation is probably
> > > > more severe though (causing sqrt + approx recip to appear)
> > > > 
> > > 
> > > Can we use UNSPEC_RSQRT14 here if UNSPEC_RSQRT28 isn't available?
> > 
> > I think we can but we lack an expander for this.  IIRC for the following
> > existing expander the RTL is ignored and thus we could simply
> > replace the TARGET_AVX512ER check with TARGET_AVX512F?
> > 
> > (define_expand "rsqrtv16sf2"
> >   [(set (match_operand:V16SF 0 "register_operand")
> >         (unspec:V16SF
> >           [(match_operand:V16SF 1 "vector_operand")]
> >           UNSPEC_RSQRT28))]
> >   "TARGET_SSE_MATH && TARGET_AVX512ER"
> > {
> >   ix86_emit_swsqrtsf (operands[0], operands[1], V16SFmode, true);
> >   DONE;
> > })
> 
> Like this?
> 
> diff --git a/gcc/config/i386/sse.md b/gcc/config/i386/sse.md
> index 3af4adc63dd..c9b4750ccc4 100644
> --- a/gcc/config/i386/sse.md
> +++ b/gcc/config/i386/sse.md
> @@ -1969,21 +1969,11 @@
>     (set_attr "mode" "<ssescalarmode>")])
>  
>  (define_expand "rsqrt<mode>2"
> -  [(set (match_operand:VF1_128_256 0 "register_operand")
> -  (unspec:VF1_128_256
> -    [(match_operand:VF1_128_256 1 "vector_operand")] UNSPEC_RSQRT))]
> +  [(set (match_operand:VF_AVX512VL 0 "register_operand")
> +  (unspec:VF_AVX512VL
> +    [(match_operand:VF_AVX512VL 1 "vector_operand")]
> +    UNSPEC_RSQRT))]
>    "TARGET_SSE_MATH"
> -{
> -  ix86_emit_swsqrtsf (operands[0], operands[1], <MODE>mode, true);
> -  DONE;
> -})
> -
> -(define_expand "rsqrtv16sf2"
> -  [(set (match_operand:V16SF 0 "register_operand")
> -  (unspec:V16SF
> -    [(match_operand:V16SF 1 "vector_operand")]
> -    UNSPEC_RSQRT28))]
> -  "TARGET_SSE_MATH && TARGET_AVX512ER"
>  {
>    ix86_emit_swsqrtsf (operands[0], operands[1], V16SFmode, true);
>    DONE;

<MODE>mode instad of V16SFmode.
>From gcc-bugs-return-630506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:35:46 2019
Return-Path: <gcc-bugs-return-630506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11501 invoked by alias); 23 Jan 2019 14:35:45 -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 11372 invoked by uid 48); 23 Jan 2019 14:35:41 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41023] Inconsistent error locations for wrong interfaces with overloaded operators
Date: Wed, 23 Jan 2019 14:35: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: unknown
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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:
Message-ID: <bug-41023-4-PWiylQ35iV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41023-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41023-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: 2019-01/txt/msg03315.txt.bz2
Content-length: 235

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

--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Has this patch ever been applied and/or reg-tested?

After a quick look to the sources, the answer is no.
>From gcc-bugs-return-630507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:37:11 2019
Return-Path: <gcc-bugs-return-630507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13718 invoked by alias); 23 Jan 2019 14:37: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 13585 invoked by uid 48); 23 Jan 2019 14:37:07 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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: attachments.created
Message-ID: <bug-88713-4-YHmFkjzeSg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03316.txt.bz2
Content-length: 224

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

--- Comment #42 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 45507
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45507&action=edit
A patch
>From gcc-bugs-return-630508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:39:56 2019
Return-Path: <gcc-bugs-return-630508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31964 invoked by alias); 23 Jan 2019 14:39:54 -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 31866 invoked by uid 48); 23 Jan 2019 14:39:50 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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: attachments.isobsolete attachments.created
Message-ID: <bug-88713-4-XWGuhwcckS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03317.txt.bz2
Content-length: 505

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45507|0                           |1
        is obsolete|                            |

--- Comment #43 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 45508
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45508&action=edit
A patch
>From gcc-bugs-return-630510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:40:49 2019
Return-Path: <gcc-bugs-return-630510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34049 invoked by alias); 23 Jan 2019 14:40:49 -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 33965 invoked by uid 48); 23 Jan 2019 14:40:43 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 14:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-LGlFZTQxNZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03319.txt.bz2
Content-length: 814

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

--- Comment #28 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Yes, it's always possible to write patterns for this, but as you point out, we
end up with many variants: insert in bottom (no left shift), insert in top
(left shift then doesn't need an additional AND mask because there are no top
bits to remove) and insert in middle.

The matching of all the immediate values to ensure that the insn makes sense is
not all that trivial - and you have to then convert those into the relevant bit
offsets during assembly output.

Finally, of course, we still have to deal with the fact that the compiler
might, somehow decide to canonicalize a pattern into the existing zero_extract
bit-field insert idiom, so we don't get to remove any insns.
>From gcc-bugs-return-630509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:40:20 2019
Return-Path: <gcc-bugs-return-630509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33114 invoked by alias); 23 Jan 2019 14:40:19 -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 33045 invoked by uid 55); 23 Jan 2019 14:40:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88984] [9 Regression] ICE in genericize_switch_stmt, at cp/cp-gimplify.c:377
Date: Wed, 23 Jan 2019 14:40: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88984-4-VOKge7m6P5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88984-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: 2019-01/txt/msg03318.txt.bz2
Content-length: 597

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 23 14:39:43 2019
New Revision: 268187

URL: https://gcc.gnu.org/viewcvs?rev=268187&root=gcc&view=rev
Log:
        PR c++/88984
        * cp-gimplify.c (genericize_switch_stmt): Move cond genericization
        before the begin_bc_block call.

        * c-c++-common/pr88984.c: New test.

Added:
    trunk/gcc/testsuite/c-c++-common/pr88984.c
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/cp-gimplify.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:41:38 2019
Return-Path: <gcc-bugs-return-630511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35713 invoked by alias); 23 Jan 2019 14:41: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 35627 invoked by uid 48); 23 Jan 2019 14:41:33 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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: attachments.isobsolete attachments.created
Message-ID: <bug-88713-4-4cBIzxQ4aY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03320.txt.bz2
Content-length: 514

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45508|0                           |1
        is obsolete|                            |

--- Comment #44 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 45509
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45509&action=edit
A combined patch
>From gcc-bugs-return-630512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:41:52 2019
Return-Path: <gcc-bugs-return-630512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36545 invoked by alias); 23 Jan 2019 14:41:52 -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 36434 invoked by uid 55); 23 Jan 2019 14:41:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/44715] Break in increment expression of "for" statement inconsistent with g++
Date: Wed, 23 Jan 2019 14:41: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-44715-4-w4hNsnDWK6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44715-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: 2019-01/txt/msg03321.txt.bz2
Content-length: 758

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 23 14:41:16 2019
New Revision: 268188

URL: https://gcc.gnu.org/viewcvs?rev=268188&root=gcc&view=rev
Log:
        PR c/44715
        * cp-gimplify.c (genericize_cp_loop): Call begin_bc_block only
        after genericizing cond and incr expressions.

        * doc/extend.texi: Document break and continue behavior in
        statement expressions.

        * c-c++-common/pr44715.c: New test.

Added:
    trunk/gcc/testsuite/c-c++-common/pr44715.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/cp-gimplify.c
    trunk/gcc/doc/extend.texi
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:47:33 2019
Return-Path: <gcc-bugs-return-630513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45153 invoked by alias); 23 Jan 2019 14:47:32 -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 45021 invoked by uid 48); 23 Jan 2019 14:47:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-LAwZZC9tHK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03322.txt.bz2
Content-length: 1267

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

--- Comment #29 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #28)
> Yes, it's always possible to write patterns for this, but as you point out,
> we end up with many variants: insert in bottom (no left shift), insert in
> top (left shift then doesn't need an additional AND mask because there are
> no top bits to remove) and insert in middle.

It is some work, sure, but I'd say not that hard and now that we have various
code/mode iterators even needs less writing.
You can have a C function used as a predicate that can also give you the right
arguments for the bfi, and I'd expect it can optimize much more than what it
could handle in the past without generic combine.c/simplify-rtx.c changes.
The problem is that if those are changed, one needs to adjust all the targets
that have carefully written patterns for this that will now no longer match and
one will need to start from scratch on all of those.  So in the end, changing
that can be much more work for many backend maintainers.
I think it is better to use define_insn_and_split and split those into the
zero_extract patterns you have when reload_completed.  rs6000 shows it can be
done.
>From gcc-bugs-return-630514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:49:47 2019
Return-Path: <gcc-bugs-return-630514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60661 invoked by alias); 23 Jan 2019 14:49:47 -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 60567 invoked by uid 48); 23 Jan 2019 14:49:41 -0000
From: "me at zv dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/89012] New: SH2 (FDPIC) duplicate symbols in generated assembly.
Date: Wed, 23 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: me at zv dot io
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89012-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: 2019-01/txt/msg03323.txt.bz2
Content-length: 1717

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

            Bug ID: 89012
           Summary: SH2 (FDPIC) duplicate symbols in generated assembly.
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: me at zv dot io
  Target Milestone: ---

Code generated by gcc targeting `sh2eb-linux-musl` occasionally
contains duplicate symbols with optimization level `O2` or above
and produces the following errors during assembly:

    $ gcc -c -mfdpic -O2 -Wno-int-conversion mintest.c
    mintest.s: Assembler messages:
    mintest.s:44: Error: symbol `.LPCS0' is already defined

This also occurs when the target is `sh2-linux-musl` but when it
specifically does not target `sh4` (even FDPIC). It does not
occur at optimization levels `O0` or `O1`.

I am using GCC with the following configuration, however, this
may also occur with 7.3.0 (unverified):

    GCC      : 8.2.0
    binutils : 2.31.1
    musl     : git-39ef61 (2018-11-19)

a minimal test case:

/* mintest.c */
int a, b, c, d;
int *e = (void *)0;
void f ()
{
    for (; d;)
    {
        if (b) c = a;
        e = e[0] = 1 << c;
    }
}

the assembly contains:

.LPCS0:
        mov.l   @r2,r0
        mov.l   r0,@r1
        mov.l   @r3,r2
        tst     r2,r2
        bt.s    .L5
        mov     r0,r1
.LPCS0:
        mov.l   r0,@r2
        mov.l   r0,@r1
        mov.l   @r3,r2
        tst     r2,r2
        bf.s    .L2
        mov     r0,r1

I could not reproduce this under 6.4.0 or 7.3.0 with binutils of
2.30 (the .LPCS0 sections are not present in the assembly).
>From gcc-bugs-return-630515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 14:51:40 2019
Return-Path: <gcc-bugs-return-630515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62772 invoked by alias); 23 Jan 2019 14:51:40 -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 62696 invoked by uid 48); 23 Jan 2019 14:51:36 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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: attachments.isobsolete attachments.created
Message-ID: <bug-88713-4-fchfEse3oS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03324.txt.bz2
Content-length: 514

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45509|0                           |1
        is obsolete|                            |

--- Comment #45 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 45510
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45510&action=edit
An updated patch
>From gcc-bugs-return-630516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:04:30 2019
Return-Path: <gcc-bugs-return-630516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45487 invoked by alias); 23 Jan 2019 15:04:29 -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 38992 invoked by uid 48); 23 Jan 2019 15:04:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 15:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-Ig6wGHCoks@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03325.txt.bz2
Content-length: 845

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

--- Comment #30 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Looking at rs6000, I see:
*rotl<mode>3_insert and *rotl<mode>3_insert_2 patterns doing what has been
discussed above (two variants for IOR operand order), *rotl<mode>3_insert_3
without one of the ANDs (not needing canonicalization), *rotl<mode>3_insert_4
with a right shift, *rotlsi3_insert_5 + *rotldi3_insert_{6,7} that match yet
something, plus rs6000_is_valid_mask and rs6000_is_valid_insert_mask helpers.
I'd say you could even copy and adjust those, add testcases that cover all that
both in the extremely small functions like in #c21 where it might be a
regression and in middle of larger code where combiner will not see hard
registers around.
A day of work at most for somebody familiar with the architecture.
>From gcc-bugs-return-630517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:13:15 2019
Return-Path: <gcc-bugs-return-630517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73437 invoked by alias); 23 Jan 2019 15:13:14 -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 73351 invoked by uid 48); 23 Jan 2019 15:13:11 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Wed, 23 Jan 2019 15:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-porDKOlJme@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-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: 2019-01/txt/msg03326.txt.bz2
Content-length: 196

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

--- Comment #31 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Please use -fdump-rtl-combine-all if you want to see the whole story.
>From gcc-bugs-return-630518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:26:27 2019
Return-Path: <gcc-bugs-return-630518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91551 invoked by alias); 23 Jan 2019 15:26:26 -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 91511 invoked by uid 48); 23 Jan 2019 15:26:23 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89013] New: ice for packed attribute
Date: Wed, 23 Jan 2019 15:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89013-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: 2019-01/txt/msg03327.txt.bz2
Content-length: 1564

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

            Bug ID: 89013
           Summary: ice for packed attribute
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

For this C source code on recent gcc trunk:

typedef struct {
} __attribute__((__packed__)) a;
typedef const a *b;
c(b *d) { b e = c(e); }

I get

bug499.c:4:1: internal compiler error: Segmentation fault
0xe5d9f7 crash_signal
        ../../trunk/gcc/toplev.c:326
0x8faba4 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*
, int, char const*)
        ../../trunk/gcc/tree.h:3289
0x8faba4 check_address_or_pointer_of_packed_member
        ../../trunk/gcc/c-family/c-warn.c:2762
0x8faba4 check_and_warn_address_or_pointer_of_packed_member
        ../../trunk/gcc/c-family/c-warn.c:2838

$ ~/gcc/results/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/dcb/gcc/results/bin/gcc
COLLECT_LTO_WRAPPER=/home/dcb/gcc/results.268100/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../trunk/configure --prefix=/home/dcb/gcc/results.268100
--disable-multilib --disable-werror --enable-checking=df,extra,fold,rtl,yes
--enable-languages=c,c++,fortran
Thread model: posix
gcc version 9.0.0 20190119 (experimental) (GCC) 
$

This seems to go wrong sometime between revision 267300 and 267400.
>From gcc-bugs-return-630519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:42:26 2019
Return-Path: <gcc-bugs-return-630519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97433 invoked by alias); 23 Jan 2019 15:42:26 -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 97394 invoked by uid 48); 23 Jan 2019 15:42:21 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] New: Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget
Message-ID: <bug-89014-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: 2019-01/txt/msg03328.txt.bz2
Content-length: 6709

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

            Bug ID: 89014
           Summary: Use-after-free in aarch64 -march=native
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dmalcolm at gcc dot gnu.org
  Target Milestone: ---
              Host: aarch64
            Target: aarch64

This downstream report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1668631
describes a problem with -march=native on aarch64 with a pre-release of gcc 9
(9.0.0-0.4.fc30.aarch64).

/usr/bin/c++  -DHAVE_NLOHMANN_JSON -I/builddir/build/BUILD/xtl-0.5.3/include 
-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
-Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables
-fstack-clash-protection -DNDEBUG   -Wunused-parameter -Wextra -Wreorder
-Wconversion -Wsign-conversion -march=native -std=gnu++14 -o
CMakeFiles/test_xcomplex_sequence.dir/test_xcomplex_sequence.cpp.o -c
/builddir/build/BUILD/xtl-0.5.3/test/test_xcomplex_sequence.cpp

Assembler messages:
Error: unknown architecture `armv8-aï¿½^&'
Error: unrecognized option -march=armv8-aï¿½^&
cc1plus: error: unknown value 'armv8-\xf0^\x17' for -march
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a
armv8.4-a armv8.5-a native; did you mean 'armv8-a'?

Note the apparent data-corruption in the error message.

This code in driver-aarch64.c looks suspicious to me:

   351    ext_string
   352      = aarch64_get_extension_string_for_isa_flags (extension_flags,
   353                                                    default_flags).c_str
();
   354  
   355    res = concat (res, ext_string, NULL);

as the std::string returned by aarch64_get_extension_string_for_isa_flags only
lives until after the call to c_str, and thus is destroyed, and so the buffer
pointed to by const char *ext_string has become invalid at line 355.

I wasn't able to reproduce the precise corruption from the above report, but
running the driver under valgrind shows:

==1326== Invalid read of size 1
==1326==    at 0x485A784: strlen (vg_replace_strmem.c:461)
==1326==    by 0x48940F: vconcat_length (concat.c:65)
==1326==    by 0x48940F: concat (concat.c:147)
==1326==    by 0x414383: host_detect_local_cpu(int, char const**)
(driver-aarch64.c:355)
==1326==    by 0x40EAEB: eval_spec_function (gcc.c:6147)
==1326==    by 0x40EAEB: handle_spec_function(char const*, bool*, char const*)
(gcc.c:6228)
==1326==    by 0x40D333: do_spec_1(char const*, int, char const*) (gcc.c:5928)
==1326==    by 0x40F61F: process_brace_body (gcc.c:6596)
==1326==    by 0x40F61F: handle_braces(char const*) (gcc.c:6503)
==1326==    by 0x40D9EB: do_spec_1(char const*, int, char const*) (gcc.c:5922)
==1326==    by 0x40E573: do_spec_2(char const*, char const*) (gcc.c:5024)
==1326==    by 0x40FA5B: do_self_spec(char const*) (gcc.c:5088)
==1326==    by 0x412B17: driver::set_up_specs() const (gcc.c:7599)
==1326==    by 0x403FAF: driver::main(int, char**) (gcc.c:7357)
==1326==    by 0x404203: main (gcc-main.c:47)
==1326==  Address 0x4b09fc0 is 0 bytes inside a block of size 61 free'd
==1326==    at 0x48588D0: operator delete(void*) (vg_replace_malloc.c:586)
==1326==    by 0x414373: deallocate (new_allocator.h:125)
==1326==    by 0x414373: deallocate (alloc_traits.h:462)
==1326==    by 0x414373: _M_destroy (basic_string.h:226)
==1326==    by 0x414373: _M_dispose (basic_string.h:221)
==1326==    by 0x414373: ~basic_string (basic_string.h:657)
==1326==    by 0x414373: host_detect_local_cpu(int, char const**)
(driver-aarch64.c:352)
==1326==    by 0x40EAEB: eval_spec_function (gcc.c:6147)
==1326==    by 0x40EAEB: handle_spec_function(char const*, bool*, char const*)
(gcc.c:6228)
==1326==    by 0x40D333: do_spec_1(char const*, int, char const*) (gcc.c:5928)
==1326==    by 0x40F61F: process_brace_body (gcc.c:6596)
==1326==    by 0x40F61F: handle_braces(char const*) (gcc.c:6503)
==1326==    by 0x40D9EB: do_spec_1(char const*, int, char const*) (gcc.c:5922)
==1326==    by 0x40E573: do_spec_2(char const*, char const*) (gcc.c:5024)
==1326==    by 0x40FA5B: do_self_spec(char const*) (gcc.c:5088)
==1326==    by 0x412B17: driver::set_up_specs() const (gcc.c:7599)
==1326==    by 0x403FAF: driver::main(int, char**) (gcc.c:7357)
==1326==    by 0x404203: main (gcc-main.c:47)
==1326==  Block was alloc'd at
==1326==    at 0x48577B0: operator new(unsigned long) (vg_replace_malloc.c:344)
==1326==    by 0x48E1C7: std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >::_M_mutate(unsigned long,
unsigned long, char const*, unsigned long) (in
/home/dmalcolm/gcc-git-bugfixing/build/gcc/xgcc)
==1326==    by 0x48FA47: std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >::_M_append(char const*, unsigned
long) (in /home/dmalcolm/gcc-git-bugfixing/build/gcc/xgcc)
==1326==    by 0x414E27: append (basic_string.h:1268)
==1326==    by 0x414E27: operator+= (basic_string.h:1178)
==1326==    by 0x414E27:
aarch64_get_extension_string_for_isa_flags[abi:cxx11](unsigned long, unsigned
long) (aarch64-common.c:323)
==1326==    by 0x41435B: host_detect_local_cpu(int, char const**)
(driver-aarch64.c:352)
==1326==    by 0x40EAEB: eval_spec_function (gcc.c:6147)
==1326==    by 0x40EAEB: handle_spec_function(char const*, bool*, char const*)
(gcc.c:6228)
==1326==    by 0x40D333: do_spec_1(char const*, int, char const*) (gcc.c:5928)
==1326==    by 0x40F61F: process_brace_body (gcc.c:6596)
==1326==    by 0x40F61F: handle_braces(char const*) (gcc.c:6503)
==1326==    by 0x40D9EB: do_spec_1(char const*, int, char const*) (gcc.c:5922)
==1326==    by 0x40E573: do_spec_2(char const*, char const*) (gcc.c:5024)
==1326==    by 0x40FA5B: do_self_spec(char const*) (gcc.c:5088)
==1326==    by 0x412B17: driver::set_up_specs() const (gcc.c:7599)

..and with "-v" that, on my test box, the "-march" value passed by the driver
to cc1 can be corrupt, or truncated.

Am testing a fix.
>From gcc-bugs-return-630520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:45:35 2019
Return-Path: <gcc-bugs-return-630520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100880 invoked by alias); 23 Jan 2019 15:45:05 -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 100758 invoked by uid 48); 23 Jan 2019 15:45:01 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 15:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89014-4-Jxjqdaygiy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03329.txt.bz2
Content-length: 246

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

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Reproducer:
  $ valgrind ./xgcc -B. -c test.c -march=native -v
(with a dummy test.c; see with today's trunk e.g. r268186)
>From gcc-bugs-return-630521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:47:01 2019
Return-Path: <gcc-bugs-return-630521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102841 invoked by alias); 23 Jan 2019 15:46:56 -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 102776 invoked by uid 48); 23 Jan 2019 15:46:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-89014-4-G9FFebFCRg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03330.txt.bz2
Content-length: 566

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2019-01-23
                 CC|                            |jakub at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |dmalcolm at gcc dot gnu.org
     Ever confirmed|0                           |1
>From gcc-bugs-return-630522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:47:52 2019
Return-Path: <gcc-bugs-return-630522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104019 invoked by alias); 23 Jan 2019 15:47:52 -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 103912 invoked by uid 48); 23 Jan 2019 15:47:47 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88933-4-NN1NpbdhGA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03331.txt.bz2
Content-length: 904

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

Martin Jambor <jamborm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jamborm at gcc dot gnu.org

--- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Martin LiÅ¡ka from comment #7)
> Created attachment 45504 [details]
> Untested patch candidate
> 
> @Martin: Can you please take a look at the patch?

I am afraid rebuilding call-graph edges would mean forgetting all
decisions to inline callees, because those are stored in
e->inline_failed, would it not?

So it seems we have to somehow update the counts (or teach the
validator to ignore these mismatches during IPA funtion transformation
and pass manager to rebuild them after all transformations).
>From gcc-bugs-return-630523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:52:22 2019
Return-Path: <gcc-bugs-return-630523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119689 invoked by alias); 23 Jan 2019 15:52: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 119570 invoked by uid 48); 23 Jan 2019 15:52:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-Qt9nFNtsQx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03332.txt.bz2
Content-length: 268

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Guess this regressed with r234877, but as -m*=native for aarch64 is supported
only since r222415, no GCC release actually supported it reliably.
>From gcc-bugs-return-630524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:54:45 2019
Return-Path: <gcc-bugs-return-630524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127197 invoked by alias); 23 Jan 2019 15:54:44 -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 127144 invoked by uid 48); 23 Jan 2019 15:54:40 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-VuQDS47Kxg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03333.txt.bz2
Content-length: 1485

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

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
The obvious fix:

diff --git a/gcc/config/aarch64/driver-aarch64.c
b/gcc/config/aarch64/driver-aarch64.c
index 2bf1f9a8c13..100e0c3529c 100644
--- a/gcc/config/aarch64/driver-aarch64.c
+++ b/gcc/config/aarch64/driver-aarch64.c
@@ -178,7 +178,6 @@ host_detect_local_cpu (int argc, const char **argv)
   unsigned int variants[2] = { ALL_VARIANTS, ALL_VARIANTS };
   unsigned int n_variants = 0;
   bool processed_exts = false;
-  const char *ext_string = "";
   unsigned long extension_flags = 0;
   unsigned long default_flags = 0;

@@ -348,11 +347,12 @@ host_detect_local_cpu (int argc, const char **argv)
   if (tune)
     return res;

-  ext_string
-    = aarch64_get_extension_string_for_isa_flags (extension_flags,
-                                                 default_flags).c_str ();
-
-  res = concat (res, ext_string, NULL);
+  {
+    std::string extension
+      = aarch64_get_extension_string_for_isa_flags (extension_flags,
+                                                   default_flags);
+    res = concat (res, extension.c_str (), NULL);
+  }

   return res;

fixes the valgrind error, but (on this box) leads to:

$ ./xgcc -B. -c test.c -march=native
Assembler messages:
Error: unknown architectural extension `rng+memtag+sb+ssbs+predres'
Error: unrecognized option -march=armv8-a+profile+rng+memtag+sb+ssbs+predres
>From gcc-bugs-return-630525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:55:59 2019
Return-Path: <gcc-bugs-return-630525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129511 invoked by alias); 23 Jan 2019 15:55:59 -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 129124 invoked by uid 48); 23 Jan 2019 15:55:55 -0000
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89012] SH2 (FDPIC) duplicate symbols in generated assembly.
Date: Wed, 23 Jan 2019 15:55: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugdal at aerifal dot cx
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89012-4-pp6TBGsEe5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89012-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: 2019-01/txt/msg03334.txt.bz2
Content-length: 609

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

--- Comment #1 from Rich Felker <bugdal at aerifal dot cx> ---
Binutils version should not be relevant; the bug here is before anything even
gets to binutils. It looks like one of the RTL patterns used for calling libgcc
bitshift functions from FDPIC was inteded to be non-duplicable but isn't. This
bug goes undetected on J2 (-mj2) target because the J2 has the SH3 barrel shift
instructions and does not need libgcc for variable shifts, but affects baseline
SH2 ISA. I'll look back at the source and see if I can figure out what's
happenning.
>From gcc-bugs-return-630526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:58:51 2019
Return-Path: <gcc-bugs-return-630526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7008 invoked by alias); 23 Jan 2019 15: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 6937 invoked by uid 48); 23 Jan 2019 15:58:46 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-Jlk09kbNpB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03335.txt.bz2
Content-length: 249

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

--- Comment #4 from ktkachov at gcc dot gnu.org ---
Yeah, the fix looks right.
For the rest of the assembler errors we need the patch at:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00562.html
>From gcc-bugs-return-630527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 15:59:36 2019
Return-Path: <gcc-bugs-return-630527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8712 invoked by alias); 23 Jan 2019 15:59:36 -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 8649 invoked by uid 48); 23 Jan 2019 15:59:32 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89008] [7/8 Regression] O2 and O1 results differ for simple test
Date: Wed, 23 Jan 2019 15:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89008-4-uD0iedp8aP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89008-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89008-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: 2019-01/txt/msg03336.txt.bz2
Content-length: 517

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

--- Comment #7 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> Created attachment 45506 [details]
> patch for the * 0 issue in reassoc
> 
> I am testing a mitigation (and missed optimization fix) in reassoc.  Bill,
> can you look into the SLSR issue which is still latent?

Yes, I'll look into it.  * 0, eh?  Yeah, I probably didn't think about that.
:-)

Probably will be a couple of days before I get to it.
>From gcc-bugs-return-630528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:07:24 2019
Return-Path: <gcc-bugs-return-630528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125458 invoked by alias); 23 Jan 2019 16:07:23 -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 123311 invoked by uid 48); 23 Jan 2019 16:07:20 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41178] Ambiguity checks for type-bound and interface operator calls
Date: Wed, 23 Jan 2019 16:07: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: domob at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-41178-4-sNddTLgPhL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41178-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41178-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: 2019-01/txt/msg03337.txt.bz2
Content-length: 281

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

--- Comment #3 from JÃ¼rgen Reuter <juergen.reuter at desy dot de> ---
Nothing has been done here for a decade, and the functions mentioned below
(gfc_expand_expr and gfc_expand_assign) do not exist any longer in the code.
>From gcc-bugs-return-630529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:09:21 2019
Return-Path: <gcc-bugs-return-630529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117694 invoked by alias); 23 Jan 2019 16:09: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 111358 invoked by uid 48); 23 Jan 2019 16:09:15 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-gKbsRQ85Tg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03338.txt.bz2
Content-length: 516

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

--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to ktkachov from comment #4)
> Yeah, the fix looks right.
> For the rest of the assembler errors we need the patch at:
> https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00562.html

Thanks; Tamar's patch at
https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01302.html changes the option
generated by the driver on this box to "-march=armv8-a", fixing the extra
errors noted in comment #3.
>From gcc-bugs-return-630530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:13:20 2019
Return-Path: <gcc-bugs-return-630530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16563 invoked by alias); 23 Jan 2019 16:13:19 -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 16184 invoked by uid 48); 23 Jan 2019 16:13:15 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 16:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-IDYVd2VCB7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03339.txt.bz2
Content-length: 3188

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

--- Comment #46 from H.J. Lu <hjl.tools at gmail dot com> ---
We generate sqrtps for scalar sqrtf:

[hjl@gnu-skx-1 pr88713]$ cat s.i
extern float sqrtf(float x);

float
rsqrt(float r)
{
  return sqrtf (r);
}
[hjl@gnu-skx-1 pr88713]$ gcc -Ofast -S s.i
[hjl@gnu-skx-1 pr88713]$ cat s.s
        .file   "s.i"
        .text
        .p2align 4,,15
        .globl  rsqrt
        .type   rsqrt, @function
rsqrt:
.LFB0:
        .cfi_startproc
        sqrtss  %xmm0, %xmm0
        ret
        .cfi_endproc
.LFE0:
        .size   rsqrt, .-rsqrt
        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
        .section        .note.GNU-stack,"",@progbits
[hjl@gnu-skx-1 pr88713]$ 

But why don't we generate sqrtps for vector sqrtf?


[hjl@gnu-skx-1 pr88713]$ cat y.i
extern float sqrtf(float x);

void
rsqrt(float* restrict r, float* restrict a){
    for (int i = 0; i < 16; i++){
        r[i] = sqrtf(a[i]);
    }
}
[hjl@gnu-skx-1 pr88713]$ gcc -S -Ofast y.i 
[hjl@gnu-skx-1 pr88713]$ cat y.s
        .file   "y.i"
        .text
        .p2align 4,,15
        .globl  rsqrt
        .type   rsqrt, @function
rsqrt:
.LFB0:
        .cfi_startproc
        movups  (%rsi), %xmm1
        pxor    %xmm2, %xmm2
        movaps  .LC0(%rip), %xmm4
        movaps  %xmm2, %xmm3
        rsqrtps %xmm1, %xmm0
        cmpneqps        %xmm1, %xmm3
        movaps  %xmm1, %xmm5
        andps   %xmm3, %xmm0
        movaps  .LC1(%rip), %xmm3
        mulps   %xmm0, %xmm5
        mulps   %xmm5, %xmm0
        mulps   %xmm3, %xmm5
        movaps  %xmm0, %xmm1
        movups  16(%rsi), %xmm0
        addps   %xmm4, %xmm1
        mulps   %xmm5, %xmm1
        movaps  %xmm2, %xmm5
        cmpneqps        %xmm0, %xmm5
        movups  %xmm1, (%rdi)
        rsqrtps %xmm0, %xmm1
        andps   %xmm5, %xmm1
        movaps  %xmm2, %xmm5
        mulps   %xmm1, %xmm0
        mulps   %xmm0, %xmm1
        mulps   %xmm3, %xmm0
        addps   %xmm4, %xmm1
        mulps   %xmm0, %xmm1
        movups  32(%rsi), %xmm0
        cmpneqps        %xmm0, %xmm5
        movups  %xmm1, 16(%rdi)
        rsqrtps %xmm0, %xmm1
        andps   %xmm5, %xmm1
        mulps   %xmm1, %xmm0
        mulps   %xmm0, %xmm1
        mulps   %xmm3, %xmm0
        addps   %xmm4, %xmm1
        mulps   %xmm0, %xmm1
        movups  %xmm1, 32(%rdi)
        movups  48(%rsi), %xmm1
        rsqrtps %xmm1, %xmm0
        cmpneqps        %xmm1, %xmm2
        andps   %xmm2, %xmm0
        mulps   %xmm0, %xmm1
        mulps   %xmm1, %xmm0
        mulps   %xmm3, %xmm1
        addps   %xmm4, %xmm0
        mulps   %xmm1, %xmm0
        movups  %xmm0, 48(%rdi)
        ret
        .cfi_endproc
.LFE0:
        .size   rsqrt, .-rsqrt
        .section        .rodata.cst16,"aM",@progbits,16
        .align 16
.LC0:
        .long   3225419776
        .long   3225419776
        .long   3225419776
        .long   3225419776
        .align 16
.LC1:
        .long   3204448256
        .long   3204448256
        .long   3204448256
        .long   3204448256
        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
        .section        .note.GNU-stack,"",@progbits
[hjl@gnu-skx-1 pr88713]$
>From gcc-bugs-return-630532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:20:56 2019
Return-Path: <gcc-bugs-return-630532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125253 invoked by alias); 23 Jan 2019 16:20:55 -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 125111 invoked by uid 48); 23 Jan 2019 16:20:51 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29670] [meta-bug] fortran interfaces
Date: Wed, 23 Jan 2019 16:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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: bug_status resolution
Message-ID: <bug-29670-4-o5Lj85gbNp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29670-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: 2019-01/txt/msg03341.txt.bz2
Content-length: 490

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29670
Bug 29670 depends on bug 41178, which changed state.

Bug 41178 Summary: Ambiguity checks for type-bound and interface operator calls
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41178

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID
>From gcc-bugs-return-630531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:20:56 2019
Return-Path: <gcc-bugs-return-630531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125245 invoked by alias); 23 Jan 2019 16:20:55 -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 125075 invoked by uid 48); 23 Jan 2019 16:20:50 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41178] Ambiguity checks for type-bound and interface operator calls
Date: Wed, 23 Jan 2019 16:20: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: domob at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-41178-4-a2ejMLM0BP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41178-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41178-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: 2019-01/txt/msg03340.txt.bz2
Content-length: 655

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Nothing has been done here for a decade, and the functions mentioned below
> (gfc_expand_expr and gfc_expand_assign) do not exist any longer in the code.

They don't even appear in the ChangeLogs, closing as INVALID.
>From gcc-bugs-return-630534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:23:51 2019
Return-Path: <gcc-bugs-return-630534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3606 invoked by alias); 23 Jan 2019 16:23:48 -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 3532 invoked by uid 48); 23 Jan 2019 16:23:45 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-OutD3VWSzC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03343.txt.bz2
Content-length: 196

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

--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01381.html
>From gcc-bugs-return-630533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:23:29 2019
Return-Path: <gcc-bugs-return-630533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2694 invoked by alias); 23 Jan 2019 16:23:28 -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 2633 invoked by uid 48); 23 Jan 2019 16:23:25 -0000
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Wed, 23 Jan 2019 16:23: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nsz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-88954-4-UkeMcBPb4Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg03342.txt.bz2
Content-length: 1266

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

nsz at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nsz at gcc dot gnu.org

--- Comment #7 from nsz at gcc dot gnu.org ---
note that with

void f_noplt(void) __attribute__((noplt));
void (*p)(void) = f_noplt;

the linker may create a PLT for f_noplt and use its address to initialize p in
case of non-pie linking.

alternatively the linker may emit a dynamic relocation for p so it is filled in
by the dynamic linker to the actual address of f_noplt.

it seems the bfd linker on x86_64 does the latter (if there is otherwise no
PLT),
but e.g. the gold linker does the former. (as far as the sysv abi is concerned
both behaviours are correct, the linker does not know about the noplt attr.)

this means that (depending on linker behaviour) a noplt function may get a PLT
in
non-pie executables (so noplt can only avoid lazy binding and jump slot relocs
reliably in pic code), may be linkers should be fixed so noplt always avoids
PLT
(on x86_64, other targets have other issues with non-pic), but then this has to
be abi to be reliable.
>From gcc-bugs-return-630535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:37:23 2019
Return-Path: <gcc-bugs-return-630535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54527 invoked by alias); 23 Jan 2019 16:37:22 -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 54455 invoked by uid 55); 23 Jan 2019 16:37:18 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 16:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-Nu7WzlSCGx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03344.txt.bz2
Content-length: 1316

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

--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Author: dmalcolm
Date: Wed Jan 23 16:36:46 2019
New Revision: 268189

URL: https://gcc.gnu.org/viewcvs?rev=268189&root=gcc&view=rev
Log:
aarch64: fix use-after-free in -march=native (PR driver/89014)

Running:
  $ valgrind ./xgcc -B. -c test.c -march=native
on aarch64 shows a use-after-free in host_detect_local_cpu due
to the std::string result of aarch64_get_extension_string_for_isa_flags
only living until immediately after a c_str call.

This leads to corrupt "-march=" values being passed to cc1.

This patch fixes the use-after-free, though it appears to also need
Tamar's patch here:
  https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01302.html
in order to generate valid values for cc1.  This may have worked by
accident in the past, if the corrupt "-march=" value happened to be
0-terminated in the "right" place; with this patch it now appears
to reliably break without Tamar's patch.

gcc/ChangeLog:
        PR driver/89014
        * config/aarch64/driver-aarch64.c (host_detect_local_cpu): Fix
        use-after-free of the result of
        aarch64_get_extension_string_for_isa_flags.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/aarch64/driver-aarch64.c
>From gcc-bugs-return-630537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:39:57 2019
Return-Path: <gcc-bugs-return-630537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93293 invoked by alias); 23 Jan 2019 16:39:56 -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 93207 invoked by uid 48); 23 Jan 2019 16:39:52 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int  type(__floatunsidf).
Date: Wed, 23 Jan 2019 16:39: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: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88877-4-BiUhydAhgc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-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: 2019-01/txt/msg03346.txt.bz2
Content-length: 268

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

--- Comment #19 from Segher Boessenkool <segher at gcc dot gnu.org> ---
As far as I can see no powerpc64 libgcc has __floatunsidf at all (or any other
soft float routines).  Where do you get those routines from?
>From gcc-bugs-return-630536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:39:19 2019
Return-Path: <gcc-bugs-return-630536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86900 invoked by alias); 23 Jan 2019 16:39:17 -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 86768 invoked by uid 48); 23 Jan 2019 16:39:14 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Wed, 23 Jan 2019 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89014-4-v1DNVKdEPP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-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: 2019-01/txt/msg03345.txt.bz2
Content-length: 603

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
The use-after-free should be fixed by r268189; -march=native on aarch64 appears
to still be broken for trunk, but at least is now broken in a deterministic,
reproducible way...
>From gcc-bugs-return-630538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:50:51 2019
Return-Path: <gcc-bugs-return-630538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119027 invoked by alias); 23 Jan 2019 16:50: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 118811 invoked by uid 55); 23 Jan 2019 16:50:44 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 16:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-dQxb0gY2g4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03347.txt.bz2
Content-length: 3645

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

--- Comment #47 from rguenther at suse dot de <rguenther at suse dot de> ---
On January 23, 2019 5:13:12 PM GMT+01:00, "hjl.tools at gmail dot com"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
>
>--- Comment #46 from H.J. Lu <hjl.tools at gmail dot com> ---
>We generate sqrtps for scalar sqrtf:
>
>[hjl@gnu-skx-1 pr88713]$ cat s.i
>extern float sqrtf(float x);
>
>float
>rsqrt(float r)
>{
>  return sqrtf (r);
>}
>[hjl@gnu-skx-1 pr88713]$ gcc -Ofast -S s.i
>[hjl@gnu-skx-1 pr88713]$ cat s.s
>        .file   "s.i"
>        .text
>        .p2align 4,,15
>        .globl  rsqrt
>        .type   rsqrt, @function
>rsqrt:
>.LFB0:
>        .cfi_startproc
>        sqrtss  %xmm0, %xmm0
>        ret
>        .cfi_endproc
>.LFE0:
>        .size   rsqrt, .-rsqrt
>        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
>        .section        .note.GNU-stack,"",@progbits
>[hjl@gnu-skx-1 pr88713]$ 
>
>But why don't we generate sqrtps for vector sqrtf?

That's the default for - mrecip back in time we benchmarked it and scalar recip
miscompares sth.

>
>[hjl@gnu-skx-1 pr88713]$ cat y.i
>extern float sqrtf(float x);
>
>void
>rsqrt(float* restrict r, float* restrict a){
>    for (int i = 0; i < 16; i++){
>        r[i] = sqrtf(a[i]);
>    }
>}
>[hjl@gnu-skx-1 pr88713]$ gcc -S -Ofast y.i 
>[hjl@gnu-skx-1 pr88713]$ cat y.s
>        .file   "y.i"
>        .text
>        .p2align 4,,15
>        .globl  rsqrt
>        .type   rsqrt, @function
>rsqrt:
>.LFB0:
>        .cfi_startproc
>        movups  (%rsi), %xmm1
>        pxor    %xmm2, %xmm2
>        movaps  .LC0(%rip), %xmm4
>        movaps  %xmm2, %xmm3
>        rsqrtps %xmm1, %xmm0
>        cmpneqps        %xmm1, %xmm3
>        movaps  %xmm1, %xmm5
>        andps   %xmm3, %xmm0
>        movaps  .LC1(%rip), %xmm3
>        mulps   %xmm0, %xmm5
>        mulps   %xmm5, %xmm0
>        mulps   %xmm3, %xmm5
>        movaps  %xmm0, %xmm1
>        movups  16(%rsi), %xmm0
>        addps   %xmm4, %xmm1
>        mulps   %xmm5, %xmm1
>        movaps  %xmm2, %xmm5
>        cmpneqps        %xmm0, %xmm5
>        movups  %xmm1, (%rdi)
>        rsqrtps %xmm0, %xmm1
>        andps   %xmm5, %xmm1
>        movaps  %xmm2, %xmm5
>        mulps   %xmm1, %xmm0
>        mulps   %xmm0, %xmm1
>        mulps   %xmm3, %xmm0
>        addps   %xmm4, %xmm1
>        mulps   %xmm0, %xmm1
>        movups  32(%rsi), %xmm0
>        cmpneqps        %xmm0, %xmm5
>        movups  %xmm1, 16(%rdi)
>        rsqrtps %xmm0, %xmm1
>        andps   %xmm5, %xmm1
>        mulps   %xmm1, %xmm0
>        mulps   %xmm0, %xmm1
>        mulps   %xmm3, %xmm0
>        addps   %xmm4, %xmm1
>        mulps   %xmm0, %xmm1
>        movups  %xmm1, 32(%rdi)
>        movups  48(%rsi), %xmm1
>        rsqrtps %xmm1, %xmm0
>        cmpneqps        %xmm1, %xmm2
>        andps   %xmm2, %xmm0
>        mulps   %xmm0, %xmm1
>        mulps   %xmm1, %xmm0
>        mulps   %xmm3, %xmm1
>        addps   %xmm4, %xmm0
>        mulps   %xmm1, %xmm0
>        movups  %xmm0, 48(%rdi)
>        ret
>        .cfi_endproc
>.LFE0:
>        .size   rsqrt, .-rsqrt
>        .section        .rodata.cst16,"aM",@progbits,16
>        .align 16
>.LC0:
>        .long   3225419776
>        .long   3225419776
>        .long   3225419776
>        .long   3225419776
>        .align 16
>.LC1:
>        .long   3204448256
>        .long   3204448256
>        .long   3204448256
>        .long   3204448256
>        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
>        .section        .note.GNU-stack,"",@progbits
>[hjl@gnu-skx-1 pr88713]$
>From gcc-bugs-return-630539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:54:21 2019
Return-Path: <gcc-bugs-return-630539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 131000 invoked by alias); 23 Jan 2019 16:54:15 -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 130918 invoked by uid 48); 23 Jan 2019 16:54:10 -0000
From: "steven.w.carmer at lmco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/89000] gcov --function-summaries says No branches/No calls, only the File summary is correct
Date: Wed, 23 Jan 2019 16:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steven.w.carmer at lmco dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89000-4-lECBXMpvzf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89000-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89000-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: 2019-01/txt/msg03348.txt.bz2
Content-length: 942

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

--- Comment #2 from Steve Carmer <steven.w.carmer at lmco dot com> ---
(In reply to Martin LiÅ¡ka from comment #1)
> I can confirm that, it's related to more complex function handling.
> I incline to remove the --function-summaries and compute the info for
> intermediate format so that one can use it in a tool.
> As mentioned, normal output is correct and one can compute the information.
> Steve, does it work for you?

We downgraded our toolchain to 7.4 because our process currently expects the
gcov output to be consistent with previous output from our heritage baseline.
We do need the output, and ideally it would be part of the -f option as in the
past, but we could pull the data from the intermediate format, as you
suggested, so once that is available we would be interested in reviewing it for
adoption into our process and tools. Thanks for your quick response.
>From gcc-bugs-return-630540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:55:52 2019
Return-Path: <gcc-bugs-return-630540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3752 invoked by alias); 23 Jan 2019 16:55:51 -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 3680 invoked by uid 48); 23 Jan 2019 16:55:47 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89015] New: [9 Regression] ICE in lookup_decl_in_outer_ctx, at omp-low.c:3480
Date: Wed, 23 Jan 2019 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89015-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: 2019-01/txt/msg03349.txt.bz2
Content-length: 1781

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

            Bug ID: 89015
           Summary: [9 Regression] ICE in lookup_decl_in_outer_ctx, at
                    omp-low.c:3480
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Changed between 20181104 and 20181111 :


$ cat z1.c
void f (int n, float *x, float *y)
{
  int i;
  int g (void)
  {
    return i;
  }
#pragma omp teams distribute parallel for simd
  for (i = 0; i < n ; i++)
    y[i] = x[i];
}


$ gcc-9-20190120 -c z1.c -fopenmp
during GIMPLE pass: omplower
z1.c: In function 'f':
z1.c:8:9: internal compiler error: in lookup_decl_in_outer_ctx, at
omp-low.c:3480
    8 | #pragma omp teams distribute parallel for simd
      |         ^~~
0x9860e8 lookup_decl_in_outer_ctx
        ../../gcc/omp-low.c:3480
0x996d87 lower_send_shared_vars
        ../../gcc/omp-low.c:6297
0x996d87 lower_omp_taskreg
        ../../gcc/omp-low.c:9000
0x98c626 lower_omp_1
        ../../gcc/omp-low.c:10416
0x98c626 lower_omp
        ../../gcc/omp-low.c:10506
0x999104 lower_omp_for
        ../../gcc/omp-low.c:8287
0x98d40e lower_omp_1
        ../../gcc/omp-low.c:10366
0x98d40e lower_omp
        ../../gcc/omp-low.c:10506
0x996ab3 lower_omp_taskreg
        ../../gcc/omp-low.c:8977
0x98e2cf lower_omp_1
        ../../gcc/omp-low.c:10416
0x98e2cf lower_omp
        ../../gcc/omp-low.c:10506
0x98d3be lower_omp_1
        ../../gcc/omp-low.c:10350
0x98d3be lower_omp
        ../../gcc/omp-low.c:10506
0x99120b execute_lower_omp
        ../../gcc/omp-low.c:10548
0x99120b execute
        ../../gcc/omp-low.c:10595
>From gcc-bugs-return-630541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:56:10 2019
Return-Path: <gcc-bugs-return-630541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9754 invoked by alias); 23 Jan 2019 16:56: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 9723 invoked by uid 48); 23 Jan 2019 16:56:06 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89015] [9 Regression] ICE in lookup_decl_in_outer_ctx, at omp-low.c:3480
Date: Wed, 23 Jan 2019 16:56: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89015-4-wf8n3mgCTo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89015-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: 2019-01/txt/msg03350.txt.bz2
Content-length: 345

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

--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---

Compiles without (unused) function g :


$ cat z2.c
void f (int n, float *x, float *y)
{
  int i;
#pragma omp teams distribute parallel for simd
  for (i = 0; i < n ; i++)
    y[i] = x[i];
}


$ gcc-9-20190120 -c z2.c -fopenmp
$
>From gcc-bugs-return-630542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 16:58:29 2019
Return-Path: <gcc-bugs-return-630542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12271 invoked by alias); 23 Jan 2019 16:58:27 -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 12185 invoked by uid 48); 23 Jan 2019 16:58:22 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/89016] New: ICE in ArrayLiteralExp::toStringExp, at d/dmd/expression.c:3873
Date: Wed, 23 Jan 2019 16:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-89016-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: 2019-01/txt/msg03351.txt.bz2
Content-length: 894

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

            Bug ID: 89016
           Summary: ICE in ArrayLiteralExp::toStringExp, at
                    d/dmd/expression.c:3873
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

With following snippets :

$ cat z1.d
deprecated([]) module m;

$ cat z2.d
deprecated([""]) module m;


$ gdc-9-20190120 -c z1.d
d21: internal compiler error: Segmentation fault
0xb821cf crash_signal
        ../../gcc/toplev.c:326
0x6a2035 ArrayLiteralExp::toStringExp()
        ../../gcc/d/dmd/expression.c:3873
0x678195 Module::importAll(Scope*)
        ../../gcc/d/dmd/dmodule.c:732
0x772d3a d_parse_file()
        ../../gcc/d/d-lang.cc:1105
>From gcc-bugs-return-630544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:01:50 2019
Return-Path: <gcc-bugs-return-630544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37896 invoked by alias); 23 Jan 2019 17:01:45 -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 37660 invoked by uid 48); 23 Jan 2019 17:01:42 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/89017] ICE in force_type_die, at dwarf2out.c:26061
Date: Wed, 23 Jan 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89017-4-NGESuAs0Lw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89017-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: 2019-01/txt/msg03353.txt.bz2
Content-length: 917

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

--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---

$ gdc-9-20190120 -c z1.d -g -O2
during GIMPLE pass: fnsplit
In function 'g':
d21: internal compiler error: in dwarf2out_abstract_function, at
dwarf2out.c:22550
0x872772 dwarf2out_abstract_function
        ../../gcc/dwarf2out.c:22550
0xbf1c89 tree_function_versioning(tree_node*, tree_node*, vec<ipa_replace_map*,
va_gc, vl_embed>*, bool, bitmap_head*, bool, bitmap_head*, basic_block_def*)
        ../../gcc/tree-inline.c:5879
0x810276 cgraph_node::create_version_clone_with_body(vec<cgraph_edge*, va_heap,
vl_ptr>, vec<ipa_replace_map*, va_gc, vl_embed>*, bitmap_head*, bool,
bitmap_head*, basic_block_def*, char const*, tree_node*)
        ../../gcc/cgraphclones.c:1078
0x12e488f split_function
        ../../gcc/ipa-split.c:1327
0x12e7a01 execute_split_functions
        ../../gcc/ipa-split.c:1825
>From gcc-bugs-return-630543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:01:23 2019
Return-Path: <gcc-bugs-return-630543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36747 invoked by alias); 23 Jan 2019 17:01: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 36687 invoked by uid 48); 23 Jan 2019 17:01:17 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/89017] New: ICE in force_type_die, at dwarf2out.c:26061
Date: Wed, 23 Jan 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot 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 target_milestone
Message-ID: <bug-89017-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: 2019-01/txt/msg03352.txt.bz2
Content-length: 1361

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

            Bug ID: 89017
           Summary: ICE in force_type_die, at dwarf2out.c:26061
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: d
          Assignee: ibuclaw at gdcproject dot org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

With option -g :


$ cat z1.d
auto f(T)()
{
  struct A(S)
  {
    class A
    {
      void g(){}
    }
  }
  return A!int();
}
void test1()
{
  f!int;
}


$ gdc-9-20190120 -c z1.d
$ gdc-9-20190120 -c z1.d -Og
$
$ gdc-9-20190120 -c z1.d -g
during RTL pass: final
z1.d: In function 'g':
z1.d:7:16: internal compiler error: in force_type_die, at dwarf2out.c:26061
    7 |       void g(){}
      |                ^
0x87f14a force_type_die
        ../../gcc/dwarf2out.c:26061
0x87f35b get_context_die
        ../../gcc/dwarf2out.c:25975
0x87f35b force_decl_die
        ../../gcc/dwarf2out.c:25994
0x877efc gen_subprogram_die
        ../../gcc/dwarf2out.c:22790
0x87a354 gen_decl_die
        ../../gcc/dwarf2out.c:26290
0x87aec6 dwarf2out_decl
        ../../gcc/dwarf2out.c:26858
0x87b4ee dwarf2out_function_decl
        ../../gcc/dwarf2out.c:26873
0x8e6459 rest_of_handle_final
        ../../gcc/final.c:4695
0x8e6459 execute
        ../../gcc/final.c:4737
>From gcc-bugs-return-630545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:05:14 2019
Return-Path: <gcc-bugs-return-630545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62074 invoked by alias); 23 Jan 2019 17:05:13 -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 61991 invoked by uid 48); 23 Jan 2019 17:05:09 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88954] __attribute__((noplt)) doesn't work with function pointers
Date: Wed, 23 Jan 2019 17:05: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-88954-4-alP7ZH0Xds@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88954-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: 2019-01/txt/msg03354.txt.bz2
Content-length: 1578

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |9.0

--- Comment #8 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to nsz from comment #7)
> note that with
> 
> void f_noplt(void) __attribute__((noplt));
> void (*p)(void) = f_noplt;
> 
> the linker may create a PLT for f_noplt and use its address to initialize p
> in
> case of non-pie linking.
> 
> alternatively the linker may emit a dynamic relocation for p so it is filled
> in
> by the dynamic linker to the actual address of f_noplt.
> 
> it seems the bfd linker on x86_64 does the latter (if there is otherwise no
> PLT),
> but e.g. the gold linker does the former. (as far as the sysv abi is
> concerned
> both behaviours are correct, the linker does not know about the noplt attr.)
> 
> this means that (depending on linker behaviour) a noplt function may get a
> PLT in
> non-pie executables (so noplt can only avoid lazy binding and jump slot
> relocs
> reliably in pic code), may be linkers should be fixed so noplt always avoids
> PLT
> (on x86_64, other targets have other issues with non-pic), but then this has
> to
> be abi to be reliable.

Gold doesn't have the same optimization as bfd linker on x86.  This is just
one of them.
>From gcc-bugs-return-630546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:10:20 2019
Return-Path: <gcc-bugs-return-630546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87581 invoked by alias); 23 Jan 2019 17:10:19 -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 87459 invoked by uid 55); 23 Jan 2019 17:10:15 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 17:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-RPyySuFkqB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03355.txt.bz2
Content-length: 1653

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

--- Comment #10 from Jan Hubicka <hubicka at ucw dot cz> ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88933
> 
> Martin Jambor <jamborm at gcc dot gnu.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |jamborm at gcc dot gnu.org
> 
> --- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> ---
> (In reply to Martin LiÅ¡ka from comment #7)
> > Created attachment 45504 [details]
> > Untested patch candidate
> > 
> > @Martin: Can you please take a look at the patch?
> 
> I am afraid rebuilding call-graph edges would mean forgetting all
> decisions to inline callees, because those are stored in
> e->inline_failed, would it not?
> 
> So it seems we have to somehow update the counts (or teach the
> validator to ignore these mismatches during IPA funtion transformation
> and pass manager to rebuild them after all transformations).

Yep, while producing the clones it is up to tree clonning to keep cgraph
up to date because edges can not be removed until inline decisions and
other transformations are applied.  The cfg cleanup there is mostly to
prevent dead basic blocks which would later kill dominance calculation
needed for SSA update.
This is done by delete_unreachable_blocks_update_callgraph is there.
Who calls merge_blocks?
I am currently travelling but I can try to take a look tonight or
tomorrow.

Honza
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.
>From gcc-bugs-return-630547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:16:47 2019
Return-Path: <gcc-bugs-return-630547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94611 invoked by alias); 23 Jan 2019 17:16:47 -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 94498 invoked by uid 55); 23 Jan 2019 17:16:32 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-wHjbYUW69l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03356.txt.bz2
Content-length: 323

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

--- Comment #11 from Jan Hubicka <hubicka at ucw dot cz> ---
Actually, looking at Martin's patch, I guess ipcp transfrom should do
the same as inliner - do not cleanup cfg but call
delete_unreachable_blocks_update_callgraph
and then go with SSA update via TODO.

Honza
>From gcc-bugs-return-630548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:17:33 2019
Return-Path: <gcc-bugs-return-630548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95729 invoked by alias); 23 Jan 2019 17:17:33 -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 95633 invoked by uid 48); 23 Jan 2019 17:17:26 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 17:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88933-4-j7EoFOSiqM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03357.txt.bz2
Content-length: 268

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

--- Comment #12 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Created attachment 45511
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45511&action=edit
Untested fix

I'm currently testing this fix.
>From gcc-bugs-return-630549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:23:41 2019
Return-Path: <gcc-bugs-return-630549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26171 invoked by alias); 23 Jan 2019 17:23:41 -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 23785 invoked by uid 48); 23 Jan 2019 17:23:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88900] [9 Regression] 502.gcc_r SPEC benchmark miscompiles with LTO and PGO
Date: Wed, 23 Jan 2019 17:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88900-4-EsJJHeNcMq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88900-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: 2019-01/txt/msg03358.txt.bz2
Content-length: 992

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

--- Comment #11 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #10)
> On Wed, 23 Jan 2019, marxin at gcc dot gnu.org wrote:
> 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88900
> > 
> > Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:
> > 
> >            What    |Removed                     |Added
> > ----------------------------------------------------------------------------
> >              Status|ASSIGNED                    |RESOLVED
> >          Resolution|---                         |INVALID
> > 
> > --- Comment #9 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
> > Yes, -fno-strict-aliasing works!
> 
> You can also try the specifc source fix to spec_qsort which IIRC
> I attached somewhere...

Yep, it's this patch:
https://github.com/freebsd/freebsd/commit/26c8a03901f609258e58c4e3bfdc981962a638f0#diff-a8e4a78e4bb28c6e0fe9561688f51573
>From gcc-bugs-return-630550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:24:46 2019
Return-Path: <gcc-bugs-return-630550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75394 invoked by alias); 23 Jan 2019 17:24:26 -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 48487 invoked by uid 48); 23 Jan 2019 17:24:04 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 17:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-sbnonBUtJd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03359.txt.bz2
Content-length: 447

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

--- Comment #13 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #11)
> Actually, looking at Martin's patch, I guess ipcp transfrom should do
> the same as inliner - do not cleanup cfg but call
> delete_unreachable_blocks_update_callgraph
> and then go with SSA update via TODO.

Oh, right, I forgot about potential clones.  Let me try the above then.
>From gcc-bugs-return-630551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:25:34 2019
Return-Path: <gcc-bugs-return-630551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16685 invoked by alias); 23 Jan 2019 17:25:34 -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 15842 invoked by uid 55); 23 Jan 2019 17:25:28 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-2bwE3y8WdV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03360.txt.bz2
Content-length: 377

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

--- Comment #14 from Jan Hubicka <hubicka at ucw dot cz> ---
> I'm currently testing this fix.
Cleanup_cfg does other transformations that makes profile to change and
statements move within bbs.  Just use the unreachable block removal
infrastructure we already have and keep it up to fixup_cfg to clean up
remaining cases.
>From gcc-bugs-return-630552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:26:20 2019
Return-Path: <gcc-bugs-return-630552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64342 invoked by alias); 23 Jan 2019 17:26:19 -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 58660 invoked by uid 55); 23 Jan 2019 17:26:15 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] [9 Regression] GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Wed, 23 Jan 2019 17:26: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88757-4-Hf8OcfY1aR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88757-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: 2019-01/txt/msg03361.txt.bz2
Content-length: 1034

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

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Jan 23 17:25:42 2019
New Revision: 268192

URL: https://gcc.gnu.org/viewcvs?rev=268192&root=gcc&view=rev
Log:
        PR c++/88757 - qualified name treated wrongly as type.
        * parser.c (cp_parser_direct_declarator): don't treat qualified-ids
        in parameter-list as types if name lookup for declarator-id didn't
        find one or more function templates.

        * g++.dg/cpp0x/dependent2.c: new test.
        * g++.dg/cpp2a/typename10.c: remove dg-error.
        * g++.dg/cpp2a/typename12.c: new test.
        * g++.dg/template/static30.c: remove dg-error.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/dependent2.C
    trunk/gcc/testsuite/g++.dg/cpp2a/typename12.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/parser.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/g++.dg/cpp2a/typename10.C
    trunk/gcc/testsuite/g++.dg/template/static30.C
>From gcc-bugs-return-630553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:27:31 2019
Return-Path: <gcc-bugs-return-630553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10120 invoked by alias); 23 Jan 2019 17:27:31 -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 5348 invoked by uid 48); 23 Jan 2019 17:27:27 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] [9 Regression] GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Wed, 23 Jan 2019 17:27: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88757-4-MrhhxLeydD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88757-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: 2019-01/txt/msg03362.txt.bz2
Content-length: 429

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:33:05 2019
Return-Path: <gcc-bugs-return-630554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23473 invoked by alias); 23 Jan 2019 17:33: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 23277 invoked by uid 48); 23 Jan 2019 17:33:00 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89013] ice for packed attribute
Date: Wed, 23 Jan 2019 17:33: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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-89013-4-LpkaQSzqRB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89013-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: 2019-01/txt/msg03363.txt.bz2
Content-length: 409

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

Arseny Solokha <asolokha at gmx dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |asolokha at gmx dot com

--- Comment #1 from Arseny Solokha <asolokha at gmx dot com> ---
Does it look similar to PR88928?
>From gcc-bugs-return-630555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:36:55 2019
Return-Path: <gcc-bugs-return-630555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45075 invoked by alias); 23 Jan 2019 17:36:54 -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 44997 invoked by uid 48); 23 Jan 2019 17:36:51 -0000
From: "kelvin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88497] Improve Accumulation in Auto-Vectorized Code
Date: Wed, 23 Jan 2019 17:36: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kelvin at gcc dot gnu.org
X-Bugzilla-Status: SUSPENDED
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88497-4-ZWnsTQzFpY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88497-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88497-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: 2019-01/txt/msg03364.txt.bz2
Content-length: 1715

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

kelvin at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |SUSPENDED
   Last reconfirmed|                            |2019-01-23
     Ever confirmed|0                           |1

--- Comment #8 from kelvin at gcc dot gnu.org ---
In revisiting this problem report, I have confirmed that if I specify
-ffast-math when I compile the original loop that motivated this problem
report, I get the desired optimization.  I believe my original discovery of
this optimization opportunity had omitted the -ffast-math option.

I have confirmed that reassociation does not produce the desired translation of
the loop body in isolation, even if -ffast-math is specified on the command
line, and even if I experiment with very large values of the
reassociation_width values for the rs6000 target.

Apparently, the reassociation pass is not clever enough to recognize
opportunities to transform multiply-add accumulations into expressions that
favor use of the xvmaddadp instruction.  Reassociation may change the order in
which the sums computed for different vector element products are combined with
the accumulator.  But in my experience, reassociation does not discover the
opportunity to accumulate the products from different vectors using vector sum
instructions or even better, the vector multiply-add instruction.

Since the code produced for -ffast-math auto-vectorization of multiply-add
accumulation loops is "optimal", I am recommending future effort on this issue
be treated as low priority.
>From gcc-bugs-return-630556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:46:41 2019
Return-Path: <gcc-bugs-return-630556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107973 invoked by alias); 23 Jan 2019 17:46:40 -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 107884 invoked by uid 48); 23 Jan 2019 17:46:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89001] g++ uses wrong mangling for lifetime-extended temporaries
Date: Wed, 23 Jan 2019 17:46: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: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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:
Message-ID: <bug-89001-4-jZUk0FnVh0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89001-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89001-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: 2019-01/txt/msg03365.txt.bz2
Content-length: 655

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
  start_mangling (variable);
  write_string ("_ZGR");
  check_abi_tags (variable);
  write_name (variable, /*ignore_local_scope=*/0);
  /* Avoid name clashes with aggregate initialization of multiple
     references at once.  */
  write_unsigned_number (temp_count++);
  return finish_mangling_get_identifier ();

So, the number we append is unique to the whole TU, rather than specific to a
particular lifetime-extended temporary.  So, we'd need to do more than just
change that write_unsigned_number call to write_compact_number.
>From gcc-bugs-return-630557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:49:42 2019
Return-Path: <gcc-bugs-return-630557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111784 invoked by alias); 23 Jan 2019 17:49:42 -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 111691 invoked by uid 48); 23 Jan 2019 17:49:38 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89013] ice for packed attribute
Date: Wed, 23 Jan 2019 17:49: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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_status resolution
Message-ID: <bug-89013-4-3kIQkZjEEr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89013-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: 2019-01/txt/msg03366.txt.bz2
Content-length: 533

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

David Binderman <dcb314 at hotmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
Yes it does look similar. Suspect duplicate.

*** This bug has been marked as a duplicate of bug 88928 ***
>From gcc-bugs-return-630558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 17:49:43 2019
Return-Path: <gcc-bugs-return-630558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111910 invoked by alias); 23 Jan 2019 17:49:43 -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 111741 invoked by uid 48); 23 Jan 2019 17:49:39 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88928] [9 Regression] ICE segfault in check_address_or_pointer_of_packed_member since r268075
Date: Wed, 23 Jan 2019 17:49: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88928-4-GgNmA2mJdL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88928-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: 2019-01/txt/msg03367.txt.bz2
Content-length: 184

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

--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
*** Bug 89013 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-630559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 18:11:49 2019
Return-Path: <gcc-bugs-return-630559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27091 invoked by alias); 23 Jan 2019 18:11: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 27006 invoked by uid 48); 23 Jan 2019 18:11:40 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 18:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-88933-4-wPpxNjuk1T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03368.txt.bz2
Content-length: 716

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

Martin Jambor <jamborm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45504|0                           |1
        is obsolete|                            |
  Attachment #45511|0                           |1
        is obsolete|                            |

--- Comment #15 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Created attachment 45512
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45512&action=edit
Another untested fix

This is what I'll be testing overnight (I have to run now).  I hope I got it
right.
>From gcc-bugs-return-630560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 18:16:55 2019
Return-Path: <gcc-bugs-return-630560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81541 invoked by alias); 23 Jan 2019 18:16:54 -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 77899 invoked by uid 48); 23 Jan 2019 18:16:49 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] [7/8/9 Regression] ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Wed, 23 Jan 2019 18:16: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88820-4-BD9jihGhgc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88820-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: 2019-01/txt/msg03369.txt.bz2
Content-length: 622

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|ICE in in C++2a mode for    |[7/8/9 Regression] ICE in
                   |code which is able to be    |in C++2a mode for code
                   |compiled in C++17 mode      |which is able to be
                   |                            |compiled in C++17 mode

--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Marking as a regression.
>From gcc-bugs-return-630561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 18:25:44 2019
Return-Path: <gcc-bugs-return-630561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116780 invoked by alias); 23 Jan 2019 18:25:44 -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 116695 invoked by uid 55); 23 Jan 2019 18:25:40 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88933] ICE: verify_cgraph_node failed (Error: caller edge count does not match BB count)
Date: Wed, 23 Jan 2019 18:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88933-4-JpptkpOgBe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88933-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: 2019-01/txt/msg03370.txt.bz2
Content-length: 340

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

--- Comment #16 from Jan Hubicka <hubicka at ucw dot cz> ---
Looks OK. I would move delete_unreachable_blocks_update_callgraph
to tree-cfgcleanup since it is no longer inliner specific.  We probably
also can sanity check that TODO_cfgcleanup is not done by ipa-transform
passes.

Honza
>From gcc-bugs-return-630562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 19:11:35 2019
Return-Path: <gcc-bugs-return-630562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 717 invoked by alias); 23 Jan 2019 19:11:34 -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 677 invoked by uid 55); 23 Jan 2019 19:11:29 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88998] [7/8/9 Regression] bad codegen with mmx instructions for unordered_map
Date: Wed, 23 Jan 2019 19:11: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uros at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88998-4-UWx7pm6jpA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88998-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: 2019-01/txt/msg03371.txt.bz2
Content-length: 687

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

--- Comment #5 from uros at gcc dot gnu.org ---
Author: uros
Date: Wed Jan 23 19:10:58 2019
New Revision: 268195

URL: https://gcc.gnu.org/viewcvs?rev=268195&root=gcc&view=rev
Log:
        PR target/88998
        * config/i386/sse.md (sse2_cvtpi2pd): Add SSE alternatives.
        Disparage MMX alternative.
        (sse2_cvtpd2pi): Ditto.
        (sse2_cvttpd2pi): Ditto.

testsuite/ChangeLog:

        PR target/88998
        * g++.target/i386/pr88998.c: New test.


Added:
    trunk/gcc/testsuite/g++.target/i386/pr88998.C
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/sse.md
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 19:16:37 2019
Return-Path: <gcc-bugs-return-630563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5814 invoked by alias); 23 Jan 2019 19:16:37 -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 5742 invoked by uid 48); 23 Jan 2019 19:16:33 -0000
From: "skpgkp1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88995] [8/9 Regression] internal compiler error: in lookup_template_class_1, at cp/pt.c:9471
Date: Wed, 23 Jan 2019 19:16: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: skpgkp1 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88995-4-jVQCmsOFJ3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88995-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: 2019-01/txt/msg03372.txt.bz2
Content-length: 4254

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

--- Comment #1 from Sunil Pandey <skpgkp1 at gmail dot com> ---
Created attachment 45513
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45513&action=edit
small reproducer.

Pass with GCC 8.2.0 but fail with mainline GCC.

GCC 8.2.0:
----------

$ gcc -O2 -fPIC -g -feliminate-unused-debug-types -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=32 -Wformat -Wformat-security
-Wl,-z,now,-z,relro,-z,max-page-size=0x1000,-z,separate-code -Wno-error
-ftree-vectorize -ftree-slp-vectorize -march=westmere -mtune=haswell
-fasynchronous-unwind-tables -fno-omit-frame-pointer -O3 -falign-functions=32 
-fno-math-errno -fno-semantic-interposition -fno-trapping-math
-Werror=return-type  -Wuninitialized -Winit-self -Wmaybe-uninitialized -O2 -g
-fvisibility=default -fopenmp -std=gnu++11  -S x.ii

$ echo $?
0

GCC Mainline:
=============

$ gcc -O2 -fPIC -g -feliminate-unused-debug-types -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=32 -Wformat -Wformat-security
-Wl,-z,now,-z,relro,-z,max-page-size=0x1000,-z,separate-code -Wno-error
-ftree-vectorize -ftree-slp-vectorize -march=westmere -mtune=haswell
-fasynchronous-unwind-tables -fno-omit-frame-pointer -O3 -falign-functions=32 
-fno-math-errno -fno-semantic-interposition -fno-trapping-math
-Werror=return-type  -Wuninitialized -Winit-self -Wmaybe-uninitialized -O2 -g
-fvisibility=default -fopenmp -std=gnu++11  -S x.ii -w

x.ii:711: internal compiler error: in lookup_template_class_1, at cp/pt.c:9471
  711 |    namespace cpu { using namespace mkldnn::impl::status; using
namespace mkldnn::impl::memory_format; using namespace mkldnn::impl::data_type;
using namespace mkldnn::impl::utils; using math::saturate; templ
      |
0x64160c lookup_template_class_1
        ../../gcc-main.42P5/gcc/cp/pt.c:9471
0x64160c lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*,
int, int)
        ../../gcc-main.42P5/gcc/cp/pt.c:9683
0x9eec7c tsubst_aggr_type
        ../../gcc-main.42P5/gcc/cp/pt.c:12686
0x9d6404 tsubst_copy
        ../../gcc-main.42P5/gcc/cp/pt.c:15462
0x9d8ff3 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:19060
0x9cf937 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:17756
0x9dfc01 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:16847
0x9dfc01 tsubst_decl
        ../../gcc-main.42P5/gcc/cp/pt.c:13779
0x9d78eb tsubst_copy
        ../../gcc-main.42P5/gcc/cp/pt.c:15507
0x9d8988 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:19259
0x9d8de4 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:18169
0x9d8599 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:18348
0x9d981f tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:18381
0x9d85e4 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:18349
0x9d8599 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:18348
0x9cf937 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:17756
0x9d4ec2 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:15346
0x9d4ec2 tsubst_init
        ../../gcc-main.42P5/gcc/cp/pt.c:15350
0x9d3f3e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:16997
0x9d124e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
        ../../gcc-main.42P5/gcc/cp/pt.c:16862
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-630564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 20:06:12 2019
Return-Path: <gcc-bugs-return-630564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115426 invoked by alias); 23 Jan 2019 20:06:12 -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 110200 invoked by uid 48); 23 Jan 2019 20:06:07 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88358] variable template definition taken as function template declaration with implicit typename
Date: Wed, 23 Jan 2019 20:06: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: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88358-4-CTV3B3CQbJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88358-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88358-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: 2019-01/txt/msg03373.txt.bz2
Content-length: 948

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I just fixed something similar: 88757.  Regarding

template <typename T>
void f(T::type);

P0634R3 says this is ill-former, but no diagnostics required.

Regarding

template <typename T>
int pi(T::your_pi); // variable template, but gcc trunk thinks this is a
function template

please see <https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01378.html>, which
fixed this for the case when the function name is a qualified-id.  I'm not sure
if there's anything to fix when it's an unqualified-id.  "pi" is I think a
simple-declaration and the core discussion didn't address this case.
>From gcc-bugs-return-630565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 20:10:31 2019
Return-Path: <gcc-bugs-return-630565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50915 invoked by alias); 23 Jan 2019 20:10:31 -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 50844 invoked by uid 48); 23 Jan 2019 20:10:27 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88846] [9 Regression] pr69776-2.c failure on 32 bit AIX
Date: Wed, 23 Jan 2019 20:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88846-4-d0wxjMo54U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88846-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: 2019-01/txt/msg03374.txt.bz2
Content-length: 326

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

--- Comment #4 from David Edelsohn <dje at gcc dot gnu.org> ---
PPC64 Linux Altivec and VSX by default while AIX does not.  PPC64 Linux loads
0.0 into FPR using VSX xxlor instruction while AIX loads via constant in
memory. This causes the different REG_EQUIV alias set.
>From gcc-bugs-return-630566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 20:20:11 2019
Return-Path: <gcc-bugs-return-630566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79316 invoked by alias); 23 Jan 2019 20:20: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 79209 invoked by uid 48); 23 Jan 2019 20:20:07 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Wed, 23 Jan 2019 20:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-iMAO7z4ISJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03375.txt.bz2
Content-length: 472

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

--- Comment #48 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to rguenther@suse.de from comment #47)
> >But why don't we generate sqrtps for vector sqrtf?
> 
> That's the default for - mrecip back in time we benchmarked it and scalar
> recip miscompares sth.

It was polyhedron benchmark, in one benchmark, the index was calculated from
square root, and that was too sensitive for 2 ULP difference.
>From gcc-bugs-return-630567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 20:21:03 2019
Return-Path: <gcc-bugs-return-630567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80791 invoked by alias); 23 Jan 2019 20:21:02 -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 80660 invoked by uid 48); 23 Jan 2019 20:20:57 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88846] [9 Regression] pr69776-2.c failure on 32 bit AIX
Date: Wed, 23 Jan 2019 20:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88846-4-851pbrMtgN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88846-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: 2019-01/txt/msg03376.txt.bz2
Content-length: 578

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

--- Comment #5 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
  There should be no REG_EQUIV as RTL doc says "it is valid for the compiler to
replace the pseudo-register by stack slot throughout the function".  In this
case the substitution results in a wrong code.

  The REG_EQUIV is produced by ira code which is an adoption of the old RA
code. The old code would do the same.  Strange that this bug did not occur long
ago.

  I've started to work on the solution.  I hope the patch will be ready this
week.
>From gcc-bugs-return-630568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:16:18 2019
Return-Path: <gcc-bugs-return-630568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57926 invoked by alias); 23 Jan 2019 21:16:18 -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 57871 invoked by uid 48); 23 Jan 2019 21:16:14 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89018] New: common subexpression present in both branches of condition is not factored out
Date: Wed, 23 Jan 2019 21:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wojciech_mula at poczta dot onet.pl
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89018-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: 2019-01/txt/msg03377.txt.bz2
Content-length: 1961

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

            Bug ID: 89018
           Summary: common subexpression present in both branches of
                    condition is not factored out
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wojciech_mula at poczta dot onet.pl
  Target Milestone: ---

A common transformation used in a C condition expression is not detected and
code is duplicated. Below are a few examples:

---condition.c---
long transform(long);

long negative_max(long a, long b) {
    return (a >= b) ? -a : -b;
}

long fun_max(long a, long b) {
    return (a >= b) ? 47*a : 47*b;
}

long transform_max(long a, long b) {
    return (a >= b) ? transform(a) : transform(b);
}
---eof---

In both branches a scalar value is a part of the same expression. So, it
would be more profitable when, for instance "(a >= b) ? -a : -b" would be
compiled as "-((a >= b) ? a : b))". Of course, a programmer might factor it
out, but in case of macros or auto-generated code such silly repetition
might occur.

Below is assembly code generated for x86 by a pretty fresh GCC 9.
BTW the jump instruction from `fun_max` and `transform_max` can
be replaced with a condition move.

$ gcc --version
gcc (GCC) 9.0.0 20190117 (experimental)

$ gcc -O3 -march=skylake -c -S condition.c && cat condition.s

negative_max:
        movq    %rdi, %rdx
        movq    %rsi, %rax
        negq    %rdx
        negq    %rax
        cmpq    %rsi, %rdi
        cmovge  %rdx, %rax
        ret

fun_max:
        cmpq    %rsi, %rdi
        jl      .L6
        imulq   $47, %rdi, %rax
        ret
.L6:
        imulq   $47, %rsi, %rax
        ret

transform_max:
        cmpq    %rsi, %rdi
        jge     .L11
        movq    %rsi, %rdi
.L11:
        jmp     transform
>From gcc-bugs-return-630569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:24:30 2019
Return-Path: <gcc-bugs-return-630569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75928 invoked by alias); 23 Jan 2019 21:24:06 -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 75156 invoked by uid 48); 23 Jan 2019 21:23:59 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87336] [8/9 regression] wrong output for pointer dummy assiocated to target actual argument
Date: Wed, 23 Jan 2019 21:24: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87336-4-dgAquCmcJb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87336-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87336-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: 2019-01/txt/msg03378.txt.bz2
Content-length: 228

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

--- Comment #6 from Harald Anlauf <anlauf at gmx dot de> ---
The patch in comment #3 seems to apply to gcc-8, but I haven't regtested it.
Paul, do you intend to backport it?
>From gcc-bugs-return-630570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:26:39 2019
Return-Path: <gcc-bugs-return-630570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87322 invoked by alias); 23 Jan 2019 21:26:39 -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 87257 invoked by uid 48); 23 Jan 2019 21:26:35 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88821] Inline packing of non-contiguous arguments
Date: Wed, 23 Jan 2019 21:26: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: 9.0
X-Bugzilla-Keywords: missed-optimization, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-88821-4-QC2uVmpOYf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88821-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: 2019-01/txt/msg03379.txt.bz2
Content-length: 583

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45486|0                           |1
        is obsolete|                            |

--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Created attachment 45514
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45514&action=edit
Patch that works plus test cases

I will defer this until stage 1 reopens.
>From gcc-bugs-return-630571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:27:20 2019
Return-Path: <gcc-bugs-return-630571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90944 invoked by alias); 23 Jan 2019 21:27:19 -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 90881 invoked by uid 48); 23 Jan 2019 21:27:14 -0000
From: "nikhil.benesch at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/89019] New: LTO and gccgo cause ICE during free_lang_data
Date: Wed, 23 Jan 2019 21:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nikhil.benesch at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
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 cc target_milestone attachments.created
Message-ID: <bug-89019-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: 2019-01/txt/msg03380.txt.bz2
Content-length: 3085

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

            Bug ID: 89019
           Summary: LTO and gccgo cause ICE during free_lang_data
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: nikhil.benesch at gmail dot com
                CC: cmang at google dot com
  Target Milestone: ---

Created attachment 45515
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45515&action=edit
patch for a partial fix

Attempting to compile the following Go program

        package main

        type fcanary func()


with LTO enabled results in the following ICE:

        go1: internal compiler error: in fld_incomplete_type_of, at tree.c:5296
        0x17858e2 fld_incomplete_type_of
                ../../gcc/tree.c:5295
        0x1786016 fld_simplified_type
                ../../gcc/tree.c:5374
        0x1787f66 free_lang_data_in_decl
                ../../gcc/tree.c:5746
        0x1789895 free_lang_data_in_cgraph
                ../../gcc/tree.c:6175
        0x1789a32 free_lang_data
                ../../gcc/tree.c:6216
        0x1789bf8 execute
                ../../gcc/tree.c:6288

System details:

        gcc version 9.0.0 20190118 (experimental) (GCC) 
        COLLECT_GCC_OPTIONS='-fsplit-stack' '-v' '-save-temps' '-flto' '-o'
'a.out' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
         /home/benesch/opt/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/go1 crash2.go
-quiet -dumpbase crash2.go -mtune=generic -march=x86-64 -auxbase crash2
-version -fsplit-stack -flto
-L/home/benesch/opt/lib/gcc/x86_64-pc-linux-gnu/9.0.0
-L/home/benesch/opt/lib/gcc/x86_64-pc-linux-gnu/9.0.0/../../../../lib64
-L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu
-L/home/benesch/opt/lib/gcc/x86_64-pc-linux-gnu/9.0.0/../../../../x86_64-pc-linux-gnu/lib
-L/home/benesch/opt/lib/gcc/x86_64-pc-linux-gnu/9.0.0/../../.. -o crash2.s
        GNU Go (GCC) version 9.0.0 20190118 (experimental)
(x86_64-pc-linux-gnu)
                compiled by GNU C version 7.3.0, GMP version 6.1.2, MPFR
version 4.0.1, MPC version 1.1.0, isl version isl-0.18-GMP

The details are rather involved. The pass that fails, free_lang_data, is only
run when compiling with LTO. This pass, as it walks the tree, makes various
assertions about the canonical type equivalence of the middle-end's expression
tree. It appears that the Go frontend is not always installing (or rather,
uninstalling) canonical types where it should, but only the free_lang_data pass
notices. It seems like this might result in subtle pointer-aliasing bugs, but
I'm not nearly familiar enough with GCC to say.

I've attached a patch that fixes the minimal reproduction I posted.
Unfortunately, in adding test coverage, I've discovered that
gcc/testsuite/go.go-torture/execute/names-1.go fails when compiled with LTO,
even with the provided patch applied. I'll post updates as I have them, but I'm
pretty out of my depth here.
>From gcc-bugs-return-630572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:31:23 2019
Return-Path: <gcc-bugs-return-630572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97811 invoked by alias); 23 Jan 2019 21:31:23 -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 97289 invoked by uid 48); 23 Jan 2019 21:31:16 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88579] Calculating power of powers of two
Date: Wed, 23 Jan 2019 21:31: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88579-4-hcTtKZEXX4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88579-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88579-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: 2019-01/txt/msg03381.txt.bz2
Content-length: 472

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk, I don't see a need for backporting.
>From gcc-bugs-return-630573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:36:22 2019
Return-Path: <gcc-bugs-return-630573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104866 invoked by alias); 23 Jan 2019 21:36: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 104801 invoked by uid 48); 23 Jan 2019 21:36:18 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88828] Inefficient update of the first element of vector registers
Date: Wed, 23 Jan 2019 21:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
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-88828-4-Qlz18wI8UC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88828-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: 2019-01/txt/msg03382.txt.bz2
Content-length: 1429

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crazylht at gmail dot com,
                   |                            |xuepeng.guo at intel dot com

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
Another testcase:

[hjl@gnu-cfl-1 pr88828]$ cat y.i
typedef double __v2df __attribute__ ((__vector_size__ (16)));
typedef double __m128d __attribute__ ((__vector_size__ (16), __may_alias__));

__m128d
_mm_add_sd (__m128d x, __m128d y)
{
  __m128d z =  __extension__ (__m128d)(__v2df)
    { (((__v2df) x)[0] + ((__v2df) y)[0]), ((__v2df) x)[1] };
  return z;
}
[hjl@gnu-cfl-1 pr88828]$  gcc -S -O2 y.i 
[hjl@gnu-cfl-1 pr88828]$  cat y.s
        .file   "y.i"
        .text
        .p2align 4,,15
        .globl  _mm_add_sd
        .type   _mm_add_sd, @function
_mm_add_sd:
.LFB0:
        .cfi_startproc
        movapd  %xmm0, %xmm2
        addsd   %xmm1, %xmm2
        movsd   %xmm2, %xmm0
        ret
        .cfi_endproc
.LFE0:
        .size   _mm_add_sd, .-_mm_add_sd
        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
        .section        .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 pr88828]$ 

I am expecting

        addsd   %xmm1, %xmm0
        retq
>From gcc-bugs-return-630574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:42:23 2019
Return-Path: <gcc-bugs-return-630574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118566 invoked by alias); 23 Jan 2019 21:42:23 -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 118482 invoked by uid 48); 23 Jan 2019 21:42:18 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85868] Subarray of a pointer array associated with a pointer dummy argument
Date: Wed, 23 Jan 2019 21:42: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: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85868-4-48UHRTkFuw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85868-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: 2019-01/txt/msg03383.txt.bz2
Content-length: 359

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

--- Comment #3 from Harald Anlauf <anlauf at gmx dot de> ---
Something has changed recently in 9-trunk, I now get with rev.268162
for the testcase in comment #0:

   2.00000000    

Printing the array bounds in subroutine te gives the expected values,
so it must be the offset that is off by one.
>From gcc-bugs-return-630575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:42:36 2019
Return-Path: <gcc-bugs-return-630575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119289 invoked by alias); 23 Jan 2019 21:42:35 -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 119248 invoked by uid 55); 23 Jan 2019 21:42:31 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88931] Inaccurate DI/TI -> SF/DF conversions in libgcc2
Date: Wed, 23 Jan 2019 21:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88931-4-huFCHlsbHq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88931-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: 2019-01/txt/msg03384.txt.bz2
Content-length: 1626

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

--- Comment #5 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Wed Jan 23 21:41:59 2019
New Revision: 268216

URL: https://gcc.gnu.org/viewcvs?rev=268216&root=gcc&view=rev
Log:
libgcc2.c: Correct DI/TI -> SF/DF conversions

FSTYPE FUNC (DWtype u) in libgcc2.c, which converts DI/TI to SF/DF, has

  /* No leading bits means u == minimum.  */
  if (count == 0)
    return -(Wtype_MAXp1_F * (Wtype_MAXp1_F / 2));

in the third case (where actually count == 0 only means the high part is
minimum).  It should be:

  /* No leading bits means u == minimum.  */
  if (count == 0)
    return Wtype_MAXp1_F * (FSTYPE) (hi | ((UWtype) u != 0));

instead.

gcc/testsuite/

2019-01-23  H.J. Lu  <hongjiu.lu@intel.com>

        PR libgcc/88931
        * gcc.dg/torture/fp-int-convert-timode-1.c: New test.
        * gcc.dg/torture/fp-int-convert-timode-2.c: Likewise.
        * gcc.dg/torture/fp-int-convert-timode-3.c: Likewise.
        * gcc.dg/torture/fp-int-convert-timode-4.c: Likewise.

libgcc/

2019-01-23  Joseph Myers  <joseph@codesourcery.com>

        PR libgcc/88931
        * libgcc2.c (FSTYPE FUNC (DWtype u)): Correct no leading bits
        case.

Added:
    trunk/gcc/testsuite/gcc.dg/torture/fp-int-convert-timode-1.c
    trunk/gcc/testsuite/gcc.dg/torture/fp-int-convert-timode-2.c
    trunk/gcc/testsuite/gcc.dg/torture/fp-int-convert-timode-3.c
    trunk/gcc/testsuite/gcc.dg/torture/fp-int-convert-timode-4.c
Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/libgcc/ChangeLog
    trunk/libgcc/libgcc2.c
>From gcc-bugs-return-630576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:43:06 2019
Return-Path: <gcc-bugs-return-630576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120340 invoked by alias); 23 Jan 2019 21:43:05 -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 120239 invoked by uid 48); 23 Jan 2019 21:43:02 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88931] Inaccurate DI/TI -> SF/DF conversions in libgcc2
Date: Wed, 23 Jan 2019 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88931-4-3qy1sVzjFw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88931-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: 2019-01/txt/msg03385.txt.bz2
Content-length: 425

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 9.
>From gcc-bugs-return-630577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:49:08 2019
Return-Path: <gcc-bugs-return-630577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 761 invoked by alias); 23 Jan 2019 21:48:52 -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 654 invoked by uid 48); 23 Jan 2019 21:48:48 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88828] Inefficient update of the first element of vector registers
Date: Wed, 23 Jan 2019 21:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse 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: see_also
Message-ID: <bug-88828-4-BXynuadgYg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88828-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: 2019-01/txt/msg03386.txt.bz2
Content-length: 488

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

Marc Glisse <glisse at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=54855

--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
Comment #3 is similar to PR 54855.
>From gcc-bugs-return-630578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 21:55:45 2019
Return-Path: <gcc-bugs-return-630578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11004 invoked by alias); 23 Jan 2019 21:55:44 -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 10934 invoked by uid 48); 23 Jan 2019 21:55:40 -0000
From: "robison at arlut dot utexas.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/89020] New: close(status='DELETE') does not remove file
Date: Wed, 23 Jan 2019 21:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: robison at arlut dot utexas.edu
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89020-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: 2019-01/txt/msg03387.txt.bz2
Content-length: 3151

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

            Bug ID: 89020
           Summary: close(status='DELETE') does not remove file
           Product: gcc
           Version: 7.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: robison at arlut dot utexas.edu
  Target Milestone: ---

Version: GNU Fortran (Ubuntu 7.2.0-8ubuntu3.2) 7.2.0
OS: Guest Ubuntu running inside Host Windows 10 using VirtualBox

Problem:

CLOSE(status='DELETE',iostat=stat) does not delete some files, and still
returns iostat == 0.

In order to delete files, I use the OPEN(file=..) followed by
CLOSE(...,status='DELETE') pattern.  Normally this works, but
it fails on VirtualBox's shared folders.  Running strace shows
that the unlink syscall happens while the file is still open,
and returns ETXTBSY, but the close then proceeds as usual.
 Testing shows that other programs are unable to unlink the
file while the fortran program has it open either, although
they can safely unlink it after a CLOSE call.

strace output:
   openat(AT_FDCWD, "/mnt/f_drive/dummyfile.xxx", O_RDWR|O_CREAT|O_CLOEXEC,
0666) = 3
   fstat(3, {st_mode=S_IFREG|0777, st_size=16, ...}) = 0
   unlink("/mnt/f_drive/dummyfile.xxx")    = -1 ETXTBSY (Text file busy)
   close(3)

I would expect one of two outputs: either the fortran CLOSE statement to note
an error, or a second unlink() is attempted after the close() syscall is
performed. 

I additionally have tried a few variations of opening it readonly, etc, but
these have no effect.

I realize this is somewhat of a corner case, but makes me wonder about
other network-mounts, where filesystems can behave a little funny.
Also, because the close(...,status='delete') is the only pure-fortran
way I know how to delete a file, I think it sees pretty wide usage.

=========================
Example Program:
Warning! this program will attempt to delete the file you provide it.
 ./a.out /path/to/file_WILL_BE_DELETED
=========================

PROGRAM file_del
implicit none

character(len=256) :: fname
integer :: xstat
logical :: file_exists

call GET_COMMAND_ARGUMENT(1,fname,status=xstat)
if (xstat .ne. 0) then
    print *, 'Required argument: Filename to create and delete'
    stop
end if

inquire(file=fname, exist=file_exists)
if (.not. file_exists) then
    open(file=fname, unit=10, iostat=xstat)
    if (xstat .ne. 0) then
        print *,'Error creating file: ',trim(fname)
        error stop 1
    else
        write(10,*) 'Dummy contents'
        close(10)
    end if
end if

20 continue
inquire(file=fname, exist=file_exists)
if (file_exists) then
    open(file=fname, unit=10, iostat=xstat)
    if (xstat .eq. 0) then
        close(10, status='DELETE', iostat=xstat)
        print *,'Closing with DELETE:',xstat
    else
        print *,'Could not open for DELETE:',xstat
    end if
    goto 20
end if

END PROGRAM file_del
>From gcc-bugs-return-630579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 22:17:16 2019
Return-Path: <gcc-bugs-return-630579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99133 invoked by alias); 23 Jan 2019 22:17:16 -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 99078 invoked by uid 48); 23 Jan 2019 22:17:12 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85868] Subarray of a pointer array associated with a pointer dummy argument
Date: Wed, 23 Jan 2019 22:17: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: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85868-4-tikfXviy1R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85868-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: 2019-01/txt/msg03388.txt.bz2
Content-length: 725

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

--- Comment #4 from Harald Anlauf <anlauf at gmx dot de> ---
Reduced testcase:

program pr85858
  implicit none
! integer, allocatable, target :: t(:)
  integer, pointer             :: t(:) => null()
  integer :: i, lb = 0  ! run under debugger, or set lb to 1
  allocate (t(lb:10))
  do i = lb, 10
     t(i) = i
  end do
  print *, t(1)
  call te (t(1:))       ! Offset should depend on 1-lb !
contains
  subroutine te (a)
    integer, pointer, intent(in) :: a(:)
    print *, a(1), lbound (a, dim=1)
  end subroutine te
end program


For lb=0 this prints

           1
           2           1

while it should print only 1s (as I get with gfortran 8.2.1).
>From gcc-bugs-return-630580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 22:44:19 2019
Return-Path: <gcc-bugs-return-630580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27133 invoked by alias); 23 Jan 2019 22:44:18 -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 27001 invoked by uid 55); 23 Jan 2019 22:44:14 -0000
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85711] ICE in aarch64_classify_address, at config/aarch64/aarch64.c:5678
Date: Wed, 23 Jan 2019 22:44: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sje at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-85711-4-hDaTlMz6cL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85711-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: 2019-01/txt/msg03389.txt.bz2
Content-length: 569

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

--- Comment #3 from Steve Ellcey <sje at gcc dot gnu.org> ---
Author: sje
Date: Wed Jan 23 22:43:42 2019
New Revision: 268219

URL: https://gcc.gnu.org/viewcvs?rev=268219&root=gcc&view=rev
Log:
2019-01-23  Bin Cheng  <bin.cheng@arm.com>
            Steve Ellcey <sellcey@marvell.com>

        PR target/85711
        * recog.c (address_operand): Return false on wrong mode for address.
        (constrain_operands): Check for mode with 'p' constraint.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/recog.c
>From gcc-bugs-return-630581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 23:13:27 2019
Return-Path: <gcc-bugs-return-630581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115978 invoked by alias); 23 Jan 2019 23:13:26 -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 115923 invoked by uid 48); 23 Jan 2019 23:13:21 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89021] New: Implement mmintrin.h in SSE
Date: Wed, 23 Jan 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-89021-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: 2019-01/txt/msg03390.txt.bz2
Content-length: 1390

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

            Bug ID: 89021
           Summary: Implement mmintrin.h in SSE
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: crazylht at gmail dot com, ubizjak at gmail dot com,
                    xuepeng.guo at intel dot com
  Target Milestone: ---
            Target: x86-64

On x86-64, __m64 is returned and passed in XMM registers. We generate

[hjl@gnu-cfl-1 pr88828]$ cat i.c
#include <mmintrin.h>

__m64
foo (__m64 x, __m64 y)
{
  return _m_packssdw (x, y);
}
[hjl@gnu-cfl-1 pr88828]$ gcc -S -O2 i.c -march=haswell
[hjl@gnu-cfl-1 pr88828]$ cat i.s
        .file   "i.c"
        .text
        .p2align 4,,15
        .globl  foo
        .type   foo, @function
foo:
.LFB129:
        .cfi_startproc
        movdq2q %xmm0, %mm0
        movdq2q %xmm1, %mm1
        packssdw        %mm1, %mm0
        movq2dq %mm0, %xmm0
        ret
        .cfi_endproc
.LFE129:
        .size   foo, .-foo
        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
        .section        .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 pr88828]$ 

We can generate

        packssdw        %xmm1, %xmm0
        ret

instead.
>From gcc-bugs-return-630582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 23 23:36:52 2019
Return-Path: <gcc-bugs-return-630582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57116 invoked by alias); 23 Jan 2019 23:36:51 -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 56095 invoked by uid 48); 23 Jan 2019 23:36:47 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/89022] New: Implement P0202R3 - C++20 Constexpr Modifiers to Functions in <algorithm> and <utility> Headers.
Date: Wed, 23 Jan 2019 23:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89022-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: 2019-01/txt/msg03391.txt.bz2
Content-length: 606

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

            Bug ID: 89022
           Summary: Implement P0202R3 - C++20 Constexpr Modifiers to
                    Functions in <algorithm> and <utility> Headers.
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: emsr at gcc dot gnu.org
  Target Milestone: ---

Almost everything in <algorithm> is constexpr.
This requires C++20 language relaxation of constexpr.
>From gcc-bugs-return-630583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 00:17:29 2019
Return-Path: <gcc-bugs-return-630583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96351 invoked by alias); 24 Jan 2019 00:17:28 -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 96311 invoked by uid 48); 24 Jan 2019 00:17:25 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/89020] close(status='DELETE') does not remove file
Date: Thu, 24 Jan 2019 00:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-89020-4-XB9hTXiwna@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89020-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: 2019-01/txt/msg03392.txt.bz2
Content-length: 1368

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to Luke Robison from comment #0)
> Version: GNU Fortran (Ubuntu 7.2.0-8ubuntu3.2) 7.2.0
> OS: Guest Ubuntu running inside Host Windows 10 using VirtualBox
> 
> Problem:
> 
> CLOSE(status='DELETE',iostat=stat) does not delete some files, and still
> returns iostat == 0.
> 
> In order to delete files, I use the OPEN(file=..) followed by
> CLOSE(...,status='DELETE') pattern.  Normally this works, but
> it fails on VirtualBox's shared folders.  Running strace shows
> that the unlink syscall happens while the file is still open,
> and returns ETXTBSY, but the close then proceeds as usual.
>  Testing shows that other programs are unable to unlink the
> file while the fortran program has it open either, although
> they can safely unlink it after a CLOSE call.
> 

If virtualbox's shared folders are doing strange things with
files or is broken, not much that the gfortran developers
can do about that.

Work around for virtualbox might 

call execute_command_line("rm -f " // filename)
>From gcc-bugs-return-630584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 00:38:12 2019
Return-Path: <gcc-bugs-return-630584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1099 invoked by alias); 24 Jan 2019 00:38:11 -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 1058 invoked by uid 48); 24 Jan 2019 00:38:07 -0000
From: "drikosev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/87199] Thread local storage dynamic initialization behaviour differs Linux vs macOS
Date: Thu, 24 Jan 2019 00:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drikosev at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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-87199-4-j9noGsGD3x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87199-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87199-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: 2019-01/txt/msg03393.txt.bz2
Content-length: 1386

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

Ev Drikos <drikosev at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |drikosev at gmail dot com

--- Comment #2 from Ev Drikos <drikosev at gmail dot com> ---
(In reply to Eric Gallager from comment #1)
> My first guess would be that the difference is Linux has native TLS, whereas
> macOS only has emutls, which would be bug 52268. I'll wait for someone else
> to confirm, though.


Not really sure if my response is indeed the confirmation you want. 

If I compile the above example in macOS High Sierra (10.13) with the much older
GNU gcc-4.8.5, then the output is "constest". Whereas with the newer gcc-8.2 I
see the same results with the OP.

$ g++ --version && uname -r
g++ (GCC) 4.8.5
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

17.5.0
$ g++  -g  -std=c++11 -c -I . main.c
$ g++  -g  -std=c++11 -c -I . lib.cpp
$ g++  -o main main.o lib.o
$ ./main
constest$ 
$ g++8  -g  -std=c++11 -c -I . main.c
$ g++8  -g  -std=c++11 -c -I . lib.cpp
$ g++8  -o main main.o lib.o
$ ./main
$

Ev. Drikos
>From gcc-bugs-return-630585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 00:39:11 2019
Return-Path: <gcc-bugs-return-630585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2546 invoked by alias); 24 Jan 2019 00:39:11 -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 2475 invoked by uid 48); 24 Jan 2019 00:39:07 -0000
From: "nikhil.benesch at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/89019] LTO and gccgo cause ICE during free_lang_data
Date: Thu, 24 Jan 2019 00:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nikhil.benesch at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-89019-4-aJAZdvE0VO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89019-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89019-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: 2019-01/txt/msg03394.txt.bz2
Content-length: 715

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

Nikhil Benesch <nikhil.benesch at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #45515|0                           |1
        is obsolete|                            |

--- Comment #1 from Nikhil Benesch <nikhil.benesch at gmail dot com> ---
Created attachment 45516
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45516&action=edit
complete patch

I tracked down the ICE revealed by names-1.go. The problem was quite similar;
placeholder structs, and not just placeholder pointers, need special handling
of TYPE_CANONICAL.
>From gcc-bugs-return-630586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 00:52:19 2019
Return-Path: <gcc-bugs-return-630586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50983 invoked by alias); 24 Jan 2019 00:52:18 -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 47512 invoked by uid 48); 24 Jan 2019 00:52:14 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/89019] LTO and gccgo cause ICE during free_lang_data
Date: Thu, 24 Jan 2019 00:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89019-4-a7I2TA5CET@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89019-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89019-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: 2019-01/txt/msg03395.txt.bz2
Content-length: 254

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

--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
Thanks for looking into this.  The patch looks fine, want to send it to
gcc-patches with a ChangeLog entry?  CC ian@golang.org.  Thanks.
>From gcc-bugs-return-630587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 01:02:40 2019
Return-Path: <gcc-bugs-return-630587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54767 invoked by alias); 24 Jan 2019 01:02:40 -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 54727 invoked by uid 48); 24 Jan 2019 01:02:35 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/89023] New: libstdc++ test failure; can't find omp.h with --disable-libgomp
Date: Thu, 24 Jan 2019 01:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89023-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: 2019-01/txt/msg03396.txt.bz2
Content-length: 1571

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

            Bug ID: 89023
           Summary: libstdc++ test failure; can't find omp.h with
                    --disable-libgomp
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sandra at gcc dot gnu.org
  Target Milestone: ---

On nios2-elf, I'm seeing

FAIL: 28_regex/headers/regex/parallel_mode.cc (test for excess errors)

Specifically:

In file included from
/path/to/nios2-elf/include/c++/9.0.0/parallel/algobase.h:40,
                 from
/path/to/nios2-elf/include/c++/9.0.0/bits/stl_algobase.h:1459,
                 from /path/to/nios2-elf/include/c++/9.0.0/algorithm:61,
                 from /path/to/nios2-elf/include/c++/9.0.0/regex:38,
                 from
/path/to/src/gcc/libstdc++-v3/testsuite/28_regex/headers/regex/parallel_mode.cc:22:
/path/to/nios2-elf/include/c++/9.0.0/parallel/base.h:37: fatal error: omp.h: No
such file or directory

I'm building for this bare-metal target with --disable-libgomp so of course
there is no omp.h being installed, and this test cannot work.

Is there some reason this test is conditionalized differently than, say, 
28_regex/headers/regex/parallel_mode.cc ??  That one is properly recognized as
unsupported on this target.

Also, the underlying failure seems related to pr35887.  Why is libstdc++ even
installing headers that depend on omp.h with --disable-libgomp?
>From gcc-bugs-return-630588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 01:40:18 2019
Return-Path: <gcc-bugs-return-630588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117374 invoked by alias); 24 Jan 2019 01:40:16 -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 117306 invoked by uid 48); 24 Jan 2019 01:40:12 -0000
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89024] New: ICE testing convertibility of incomplete enumeration types
Date: Thu, 24 Jan 2019 01:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rs2740 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89024-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: 2019-01/txt/msg03397.txt.bz2
Content-length: 3159

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

            Bug ID: 89024
           Summary: ICE testing convertibility of incomplete enumeration
                    types
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rs2740 at gmail dot com
  Target Milestone: ---

Reduced:

template<class T> T&& declval();

template<typename _To1>
void __test_aux(_To1);

template<typename _From1, typename _To1,
        typename = decltype(__test_aux<_To1>(declval<_From1>()))>
char __test(int);

template<typename, typename>
int __test(...);

enum E {
    x = decltype(__test<E, int>(0))(0);
};

prog.cc: In substitution of 'template<class _From1, class _To1, class> char
__test(int) [with _From1 = E; _To1 = int; <template-parameter-1-3> =
<missing>]':
prog.cc:14:34:   required from here
prog.cc:7:45: internal compiler error: Segmentation fault
    7 |         typename = decltype(__test_aux<_To1>(declval<_From1>()))>
      |                             ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
0xb80c8f crash_signal
        ../../source/gcc/toplev.c:326
0x61d43e type_promotes_to(tree_node*)
        ../../source/gcc/cp/cvt.c:1916
0x5df449 standard_conversion
        ../../source/gcc/cp/call.c:1418
0x5e541b implicit_conversion
        ../../source/gcc/cp/call.c:1865
0x5e664a add_function_candidate
        ../../source/gcc/cp/call.c:2255
0x5e7045 add_template_candidate_real
        ../../source/gcc/cp/call.c:3284
0x5e7574 add_template_candidate
        ../../source/gcc/cp/call.c:3325
0x5e7574 add_candidates
        ../../source/gcc/cp/call.c:5618
0x5e7933 add_candidates
        ../../source/gcc/cp/call.c:4284
0x5e7933 perform_overload_resolution
        ../../source/gcc/cp/call.c:4292
0x5eb045 build_new_function_call(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, int)
        ../../source/gcc/cp/call.c:4366
0x6fd760 finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
        ../../source/gcc/cp/semantics.c:2568
0x6d43ed tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../source/gcc/cp/pt.c:18874
0x6dbd8c tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
        ../../source/gcc/cp/pt.c:14991
0x6dbd8c tsubst(tree_node*, tree_node*, int, tree_node*)
        ../../source/gcc/cp/pt.c:14991
0x6e8ff2 type_unification_real
        ../../source/gcc/cp/pt.c:20874
0x6e9b80 fn_type_unification(tree_node*, tree_node*, tree_node*, tree_node*
const*, unsigned int, tree_node*, unification_kind_t, int, conversion**, bool,
bool)
        ../../source/gcc/cp/pt.c:20066
0x5e6e20 add_template_candidate_real
        ../../source/gcc/cp/call.c:3240
0x5e7574 add_template_candidate
        ../../source/gcc/cp/call.c:3325
0x5e7574 add_candidates
        ../../source/gcc/cp/call.c:5618
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-630589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 01:45:48 2019
Return-Path: <gcc-bugs-return-630589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123113 invoked by alias); 24 Jan 2019 01:45:47 -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 122791 invoked by uid 48); 24 Jan 2019 01:45:26 -0000
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89025] New: Wrong point of declaration for enumeration names
Date: Thu, 24 Jan 2019 01:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rs2740 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89025-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: 2019-01/txt/msg03398.txt.bz2
Content-length: 971

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

            Bug ID: 89025
           Summary: Wrong point of declaration for enumeration names
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: accepts-invalid, rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rs2740 at gmail dot com
  Target Milestone: ---

Per [basic.scope.pdecl]/3,

> The point of declaration for an enumeration is immediately after 
> the identifier (if any) in either its enum-specifier ([dcl.enum])
> or its first opaque-enum-declaration ([dcl.enum]), whichever comes first.

GCC appears to treat the enumeration as undeclared until after the enum-base:

template<class> using int_ = int;

enum E : int_<E> {}; // should be OK, but error

using E1 = long;

namespace {
    enum E1 : E1 {}; // should be error, but accepted
}
>From gcc-bugs-return-630590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 02:26:16 2019
Return-Path: <gcc-bugs-return-630590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123871 invoked by alias); 24 Jan 2019 02:26:15 -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 123802 invoked by uid 48); 24 Jan 2019 02:26:12 -0000
From: "felipe at expertisesolutions dot com.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89026] New: [mingw] -I directives in response files assume C:/ as '/', but C:/msys2 when passed directly
Date: Thu, 24 Jan 2019 02:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: felipe at expertisesolutions dot com.br
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89026-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: 2019-01/txt/msg03399.txt.bz2
Content-length: 1194

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

            Bug ID: 89026
           Summary: [mingw] -I directives in response files assume C:/ as
                    '/', but C:/msys2 when passed directly
           Product: gcc
           Version: 7.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: felipe at expertisesolutions dot com.br
  Target Milestone: ---

If you create a response file with the following content:

<file abc.rsp>
-I/mingw64/include/dbus-1.0 -c -o abc.o abc
</file>

and call the compiler to the following C file:
<file abc.c>
#include <dbus/dbus.h>
</file>

With the following parameters:

gcc @abc.rsp

it will return that it did not find dbus/dbus.h. However, if you call with the
following parameters:

gcc -I/mingw64/include/dbus-1.0 -c -o abc.o abc

Then the compilation errors on another header that dbus.h tries to include.

Also, the response file works (complaining about other header inside dbus.h)
when we change it like this:

<file abc.rsp>
-I/msys64/mingw64/include/dbus-1.0 -c -o abc.o abc
</file>


Regards,
>From gcc-bugs-return-630591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 02:50:39 2019
Return-Path: <gcc-bugs-return-630591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34532 invoked by alias); 24 Jan 2019 02:50: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 34440 invoked by uid 48); 24 Jan 2019 02:50:33 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89027] New: [9 Regression] ICE: verify_gimple failed (Error: non-trivial conversion at assignment)
Date: Thu, 24 Jan 2019 02:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89027-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: 2019-01/txt/msg03400.txt.bz2
Content-length: 2120

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

            Bug ID: 89027
           Summary: [9 Regression] ICE: verify_gimple failed (Error:
                    non-trivial conversion at assignment)
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Keywords: ice-checking, ice-on-valid-code, openmp
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---

gfortran-9.0.0-alpha20190120 snapshot (r268107) ICEs when compiling the
following testcase reduced from libgomp/testsuite/libgomp.fortran/nestedfn5.f90
w/ -O2 -fexceptions -fopenmp -fno-tree-dce:

subroutine bar
  integer :: a, b
  a = 1
  b = 2
  call foo
contains
  subroutine foo
!$omp simd linear(a:2) linear(b:1)
    do a = 1, 20, 2
      b = b + 1
    end do
!$omp end simd
    if (a /= 21 .or. b /= 12) STOP 1
!$omp task depend(out : a)
    a = a + 1
!$omp end task
  end subroutine foo
end subroutine bar

% powerpc-e300c3-linux-gnu-gfortran-9.0.0-alpha20190120 -mvsx -O2 -fexceptions
-fopenmp -fno-tree-dce -c epm9nnl9.f90
epm9nnl9.f90:1:0:

    1 | subroutine bar
      | 
Error: non-trivial conversion at assignment
integer(kind=4)[4]
integer(kind=4)[16]
# .MEM_40 = VDEF <.MEM_39>
D.2257 ={v} {CLOBBER};
during GIMPLE pass: vect
epm9nnl9.f90:1:0: internal compiler error: verify_gimple failed
0xdebaf9 verify_gimple_in_cfg(function*, bool)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/tree-cfg.c:5422
0xcc1e0e execute_function_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:1977
0xcc27aa execute_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190120/work/gcc-9-20190120/gcc/passes.c:2031

(While my target here is powerpc, the ICE is not target-specific. It can be
reproduced on x86_64 as well, obviously w/o -mvsx.)
>From gcc-bugs-return-630592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 02:56:46 2019
Return-Path: <gcc-bugs-return-630592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19151 invoked by alias); 24 Jan 2019 02:56: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 16932 invoked by uid 48); 24 Jan 2019 02:56:42 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89024] [7/8/9 Regression] ICE testing convertibility of incomplete enumeration types
Date: Thu, 24 Jan 2019 02:56: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-89024-4-nBKMoylXRT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89024-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: 2019-01/txt/msg03401.txt.bz2
Content-length: 1333

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-24
                 CC|                            |mpolacek at gcc dot gnu.org
   Target Milestone|---                         |7.5
            Summary|ICE testing convertibility  |[7/8/9 Regression] ICE
                   |of incomplete enumeration   |testing convertibility of
                   |types                       |incomplete enumeration
                   |                            |types
     Ever confirmed|0                           |1

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.  

Started with r159006, it's a regression.

A valid version:

template<class T> T&& declval();

template<typename _To1>
void __test_aux(_To1);

template<typename _From1, typename _To1,
        typename = decltype(__test_aux<_To1>(declval<_From1>()))>
char __test(int);

template<typename, typename>
int __test(...);

enum E {
    x = decltype(__test<E, int>(0))(0);
};
>From gcc-bugs-return-630593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 02:57:32 2019
Return-Path: <gcc-bugs-return-630593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44373 invoked by alias); 24 Jan 2019 02:57:31 -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 42344 invoked by uid 48); 24 Jan 2019 02:57:28 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89024] [7/8/9 Regression] ICE testing convertibility of incomplete enumeration types
Date: Thu, 24 Jan 2019 02:57: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89024-4-JfEwNj1Qzr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89024-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: 2019-01/txt/msg03402.txt.bz2
Content-length: 535

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

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #1)
> A valid version:

Eh, this one (without the semicolon):

template<class T> T&& declval();

template<typename _To1>
void __test_aux(_To1);

template<typename _From1, typename _To1,
        typename = decltype(__test_aux<_To1>(declval<_From1>()))>
char __test(int);

template<typename, typename>
int __test(...);

enum E {
    x = decltype(__test<E, int>(0))(0)
};
>From gcc-bugs-return-630594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 02:58:52 2019
Return-Path: <gcc-bugs-return-630594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81559 invoked by alias); 24 Jan 2019 02:58:51 -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 79584 invoked by uid 48); 24 Jan 2019 02:58:47 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89028] New: 8-byte loop isn't vectorized
Date: Thu, 24 Jan 2019 02:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89028-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: 2019-01/txt/msg03403.txt.bz2
Content-length: 1194

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

            Bug ID: 89028
           Summary: 8-byte loop isn't vectorized
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
  Target Milestone: ---

[hjl@gnu-skx-1 v64-2]$ cat y.i
void
rsqrt(char* restrict r, char* restrict a){
    for (int i = 0; i < 8; i++){
        r[i] += a[i];
    }
}
[hjl@gnu-skx-1 v64-2]$ gcc -S -O2 y.i
[hjl@gnu-skx-1 v64-2]$ cat y.s
        .file   "y.i"
        .text
        .p2align 4,,15
        .globl  rsqrt
        .type   rsqrt, @function
rsqrt:
.LFB0:
        .cfi_startproc
        xorl    %eax, %eax
        .p2align 4,,10
        .p2align 3
.L2:
        movzbl  (%rsi,%rax), %edx
        addb    %dl, (%rdi,%rax)
        addq    $1, %rax
        cmpq    $8, %rax
        jne     .L2
        ret
        .cfi_endproc
.LFE0:
        .size   rsqrt, .-rsqrt
        .ident  "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
        .section        .note.GNU-stack,"",@progbits
[hjl@gnu-skx-1 v64-2]$
>From gcc-bugs-return-630595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 03:01:17 2019
Return-Path: <gcc-bugs-return-630595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22272 invoked by alias); 24 Jan 2019 03:01:16 -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 22157 invoked by uid 48); 24 Jan 2019 03:01:12 -0000
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89024] [7/8/9 Regression] ICE testing convertibility of incomplete enumeration types
Date: Thu, 24 Jan 2019 03:01: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rs2740 at gmail dot com
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89024-4-IokRv1Pg98@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89024-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: 2019-01/txt/msg03404.txt.bz2
Content-length: 209

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89024

--- Comment #3 from TC <rs2740 at gmail dot com> ---
Bah, must have copy-pasta'd the semicolon somewhere when reducing the original
and didn't notice :(
>From gcc-bugs-return-630596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 03:11:12 2019
Return-Path: <gcc-bugs-return-630596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31794 invoked by alias); 24 Jan 2019 03:11:11 -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 31710 invoked by uid 48); 24 Jan 2019 03:11:06 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88993] GCC 9 -Wformat-overflow=2 should reflect real libc limits
Date: Thu, 24 Jan 2019 03:11: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-88993-4-K5G1gpi3Cn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88993-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: 2019-01/txt/msg03405.txt.bz2
Content-length: 854

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88993

--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
For some background into the source of the limit see the discussion below:
  https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01772.html
The warning is based on the C limit in the discussion and the Glibc
bug/limitation discussed in it.

I certainly agree with making Glibc's sprintf more robust by avoiding dynamic
memory allocation but that (unfortunately) won't let GCC remove the limit.

I'm open to adjusting the warning to make it more useful if it's causing
trouble.  It's not clear to me yet that it is causing enough trouble to justify
making a change to it at this stage of GCC development.

Richard, can you give us an idea of how much trouble this is causing and what
the impact would be of not suppressing it in GCC 9?
>From gcc-bugs-return-630597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 03:43:13 2019
Return-Path: <gcc-bugs-return-630597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22682 invoked by alias); 24 Jan 2019 03:43:12 -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 22648 invoked by uid 48); 24 Jan 2019 03:43:08 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89024] [7/8/9 Regression] ICE testing convertibility of incomplete enumeration types
Date: Thu, 24 Jan 2019 03:43: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-89024-4-FoJfgA897K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89024-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: 2019-01/txt/msg03406.txt.bz2
Content-length: 512

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89024

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |mpolacek at gcc dot gnu.org

--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
No worries and thanks for filing the PR.  Testing a patch.
>From gcc-bugs-return-630598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 03:59:52 2019
Return-Path: <gcc-bugs-return-630598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39980 invoked by alias); 24 Jan 2019 03:59:51 -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 39924 invoked by uid 48); 24 Jan 2019 03:59:47 -0000
From: "pdimov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89029] New: __builtin_constant_p erroneously true
Date: Thu, 24 Jan 2019 03:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pdimov at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89029-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: 2019-01/txt/msg03407.txt.bz2
Content-length: 1712

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89029

            Bug ID: 89029
           Summary: __builtin_constant_p erroneously true
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pdimov at gmail dot com
  Target Milestone: ---

In the following code:

```
inline bool assert_static_check( bool ev )
{
    return __builtin_constant_p( ev ) && !ev;
}

struct X1
{
    int v1_;
};

inline bool operator==( X1 const& x1, X1 const& x2 )
{
    return x1.v1_ == x2.v1_;
}

int compare( X1 s1, X1 s2 )
{
    return assert_static_check( s1 == s2 );
}

struct X2
{
    int v1_;
    int v2_;
};

inline bool operator==( X2 const& x1, X2 const& x2 )
{
    return x1.v1_ == x2.v1_ && x1.v2_ == x2.v2_;
}

int compare( X2 s1, X2 s2 )
{
    return assert_static_check( s1 == s2 );
}
```

the generated code for the first compare function is, correctly,

```
compare(X1, X1):
        xor     eax, eax
        ret
```

but for the second, it is

```
compare(X2, X2):
        mov     eax, 1
        cmp     edi, esi
        je      .L6
        ret
.L6:
        sar     rdi, 32
        sar     rsi, 32
        xor     eax, eax
        cmp     edi, esi
        setne   al
        ret
```

which is incorrect, as `s1 == s2` isn't a constant here.

(g++ -std=c++17 -O3, https://godbolt.org/z/nn0-4k)

(This is simplified from an attempt to create a statically-diagnosed assert
facility that would warn when the asserted expression is known to be false:
https://godbolt.org/z/i5SXSd. Would've been cool if it worked.)
>From gcc-bugs-return-630599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 04:17:12 2019
Return-Path: <gcc-bugs-return-630599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4190 invoked by alias); 24 Jan 2019 04:17:11 -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 4158 invoked by uid 48); 24 Jan 2019 04:17:07 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63440] -Og does enable -fmerge-constants too
Date: Thu, 24 Jan 2019 04:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager 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:
Message-ID: <bug-63440-4-BLZH0ho0rs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63440-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63440-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: 2019-01/txt/msg03408.txt.bz2
Content-length: 355

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63440

--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Richard Biener from comment #1)
> > Note that the various "Enabled at levels ..." were not updated for -Og.
> 
> This part is bug 59658.

...which Sandra has since fixed.
>From gcc-bugs-return-630600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 04:23:00 2019
Return-Path: <gcc-bugs-return-630600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23361 invoked by alias); 24 Jan 2019 04:23:00 -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 23317 invoked by uid 48); 24 Jan 2019 04:22:56 -0000
From: "felipe at expertisesolutions dot com.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89026] [mingw] -I directives in response files assume C:/ as '/', but C:/msys2 when passed directly
Date: Thu, 24 Jan 2019 04:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: felipe at expertisesolutions dot com.br
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89026-4-MlQPl1DMdS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89026-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89026-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: 2019-01/txt/msg03409.txt.bz2
Content-length: 200

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89026

--- Comment #1 from Felipe Magno de Almeida <felipe at expertisesolutions dot com.br> ---
Tested on GCC 7.4.0 and it doesn't show the same bug.
>From gcc-bugs-return-630601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 04:26:32 2019
Return-Path: <gcc-bugs-return-630601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27816 invoked by alias); 24 Jan 2019 04:26:31 -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 27751 invoked by uid 48); 24 Jan 2019 04:26:27 -0000
From: "felipe at expertisesolutions dot com.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89026] [mingw] -I directives in response files assume C:/ as '/', but C:/msys2 when passed directly
Date: Thu, 24 Jan 2019 04:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: felipe at expertisesolutions dot com.br
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89026-4-oz9FYWxWAy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89026-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89026-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: 2019-01/txt/msg03410.txt.bz2
Content-length: 233

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89026

--- Comment #2 from Felipe Magno de Almeida <felipe at expertisesolutions dot com.br> ---
Also happens when I call cc1 directly. So, it doesn't seem to be the driver's
fault.
>From gcc-bugs-return-630602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 05:35:35 2019
Return-Path: <gcc-bugs-return-630602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48176 invoked by alias); 24 Jan 2019 05:35:34 -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 48129 invoked by uid 48); 24 Jan 2019 05:35:31 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89030] New: gfortran accepts invalid code
Date: Thu, 24 Jan 2019 05:35: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89030-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: 2019-01/txt/msg03411.txt.bz2
Content-length: 1468

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89030

            Bug ID: 89030
           Summary: gfortran accepts invalid code
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: juergen.reuter at desy dot de
  Target Milestone: ---

The following issue was discussed on the Intel forum:
https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/803316
The assignment is accepted by gfortran, but it should be rejected as invalid
code:
x = t(5)

1. The RHS is evaluated as structure constructor for t
2. Then defined assignment sets in, so it is translated into set (x, t(5)),
and here either both x and t must be unlimited polymorphic, or both
have to have the same type.
(if I understand the standard correctly, but Steve Lionel seems to support
this)
Cheers,
    JRR



Short reproducer:


module mod

  implicit none
  private

  type, public :: t
     integer :: i = 3
   contains
     generic, public :: assignment(=) => set
     procedure, private :: set
  end type t

contains

  subroutine set(x, y)
    class(t), intent(out) :: x
    type(t), intent(in) :: y
    print *, "foo"
  end subroutine set

end module mod



program alloc_assign

  use mod
  implicit none
  class(*), allocatable :: x

  x = t(5)

end program alloc_assign
>From gcc-bugs-return-630603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 06:03:55 2019
Return-Path: <gcc-bugs-return-630603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22937 invoked by alias); 24 Jan 2019 06:03:54 -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 22835 invoked by uid 48); 24 Jan 2019 06:03:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89029] __builtin_constant_p erroneously true
Date: Thu, 24 Jan 2019 06:03: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-89029-4-aNzs1AItsQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89029-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89029-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: 2019-01/txt/msg03412.txt.bz2
Content-length: 616

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89029

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
See e.g. PR72785, using __builtin_constant_p this way isn't really going to
work reliably, it is folded too late and jump threading and other optimizations
may cause it to be evaluated to 1 in some part of a function and 0 in another.
>From gcc-bugs-return-630604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 07:14:17 2019
Return-Path: <gcc-bugs-return-630604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59639 invoked by alias); 24 Jan 2019 07:14:16 -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 57156 invoked by uid 48); 24 Jan 2019 07:14:13 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Thu, 24 Jan 2019 07:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-w4OPj2zjdF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03413.txt.bz2
Content-length: 600

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713

--- Comment #49 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to UroÅ¡ Bizjak from comment #48)
> (In reply to rguenther@suse.de from comment #47)
> > >But why don't we generate sqrtps for vector sqrtf?
> > 
> > That's the default for - mrecip back in time we benchmarked it and scalar
> > recip miscompares sth.
> 
> It was polyhedron benchmark, in one benchmark, the index was calculated from
> square root, and that was too sensitive for 2 ULP difference.

Argh.  Sacrificing performance for the sake of bugware...
>From gcc-bugs-return-630605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 07:20:26 2019
Return-Path: <gcc-bugs-return-630605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18767 invoked by alias); 24 Jan 2019 07:20:25 -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 18702 invoked by uid 55); 24 Jan 2019 07:20:21 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Thu, 24 Jan 2019 07:20: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88929-4-0SaMfb6fpF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg03414.txt.bz2
Content-length: 1334

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88929

--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Thu Jan 24 07:19:49 2019
New Revision: 268231

URL: https://gcc.gnu.org/viewcvs?rev=268231&root=gcc&view=rev
Log:
2019-01-24  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/88929
        * trans-array.c (gfc_conv_descriptor_elem_len): New function.
        * trans-array.h : Add prototype for above.
        * trans-expr.c (gfc_conv_gfc_desc_to_cfi_desc): Take account of
        assumed rank arrays being flagged by rank = -1 in expressions.
        Intent in arrays need a pointer to a copy of the data to be
        assigned to the descriptor passed for conversion. This should
        then be freed, together with the CFI descriptor on return from
        the C call.

2019-01-24  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/88929
        * gfortran.dg/ISO_Fortran_binding_3.f90 : New test
        * gfortran.dg/ISO_Fortran_binding_3.c : Subsidiary source.

Added:
    trunk/gcc/testsuite/gfortran.dg/ISO_Fortran_binding_3.c
    trunk/gcc/testsuite/gfortran.dg/ISO_Fortran_binding_3.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-array.c
    trunk/gcc/fortran/trans-array.h
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-630606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 07:22:12 2019
Return-Path: <gcc-bugs-return-630606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21761 invoked by alias); 24 Jan 2019 07:22:12 -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 21709 invoked by uid 55); 24 Jan 2019 07:22:08 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Thu, 24 Jan 2019 07:22: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88929-4-pbLnId1yCw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg03415.txt.bz2
Content-length: 1094

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88929

--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Thu Jan 24 07:21:36 2019
New Revision: 268232

URL: https://gcc.gnu.org/viewcvs?rev=268232&root=gcc&view=rev
Log:
2019-01-24  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/88929
        * trans-array.c (gfc_conv_descriptor_elem_len): New function.
        * trans-array.h : Add prototype for above.
        * trans-expr.c (gfc_conv_gfc_desc_to_cfi_desc): Take account of
        assumed rank arrays being flagged by rank = -1 in expressions.
        Intent in arrays need a pointer to a copy of the data to be
        assigned to the descriptor passed for conversion. This should
        then be freed, together with the CFI descriptor on return from
        the C call.

2019-01-24  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/88929
        * gfortran.dg/ISO_Fortran_binding_3.f90 : New test
        * gfortran.dg/ISO_Fortran_binding_3.c : Subsidiary source.

Modified:
    trunk/gcc/testsuite/gfortran.dg/ISO_Fortran_binding_3.f90
>From gcc-bugs-return-630607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 07:23:25 2019
Return-Path: <gcc-bugs-return-630607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23635 invoked by alias); 24 Jan 2019 07:23:25 -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 23548 invoked by uid 48); 24 Jan 2019 07:23:21 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88929] ICE on building MPICH 3.2 with GCC 9 with ISO_Fortran_binding
Date: Thu, 24 Jan 2019 07:23: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88929-4-11wLw9fZ9U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88929-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: 2019-01/txt/msg03416.txt.bz2
Content-length: 434

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88929

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on trunk.

Paul
>From gcc-bugs-return-630608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 07:36:25 2019
Return-Path: <gcc-bugs-return-630608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84498 invoked by alias); 24 Jan 2019 07:36:25 -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 84436 invoked by uid 48); 24 Jan 2019 07:36:22 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89021] Implement mmintrin.h in SSE
Date: Thu, 24 Jan 2019 07:36: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89021-4-NOZW7NcXZx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89021-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89021-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: 2019-01/txt/msg03417.txt.bz2
Content-length: 266

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89021

--- Comment #1 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
Porbably we just need to add SSE alternatives to existing MMX builtins. C.f.
[1].

[1] https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01393.html
>From gcc-bugs-return-630609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 07:46:48 2019
Return-Path: <gcc-bugs-return-630609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130116 invoked by alias); 24 Jan 2019 07:46:48 -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 130049 invoked by uid 48); 24 Jan 2019 07:46:44 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Thu, 24 Jan 2019 07:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-0ab5Am93PR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03418.txt.bz2
Content-length: 800

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713

--- Comment #50 from UroÅ¡ Bizjak <ubizjak at gmail dot com> ---
(In reply to Thomas Koenig from comment #49)
> (In reply to UroÅ¡ Bizjak from comment #48)
> > (In reply to rguenther@suse.de from comment #47)
> > > >But why don't we generate sqrtps for vector sqrtf?
> > > 
> > > That's the default for - mrecip back in time we benchmarked it and scalar
> > > recip miscompares sth.
> > 
> > It was polyhedron benchmark, in one benchmark, the index was calculated from
> > square root, and that was too sensitive for 2 ULP difference.
> 
> Argh.  Sacrificing performance for the sake of bugware...

The details are in [1] and all the drama is documented in PR32352.

[1] https://gcc.gnu.org/ml/gcc-patches/2007-06/msg01044.html
>From gcc-bugs-return-630610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:14:50 2019
Return-Path: <gcc-bugs-return-630610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5730 invoked by alias); 24 Jan 2019 08:14:49 -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 5679 invoked by uid 48); 24 Jan 2019 08:14:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89027] [9 Regression] ICE: verify_gimple failed (Error: non-trivial conversion at assignment)
Date: Thu, 24 Jan 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on cc cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-89027-4-QeD8Q29bi0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89027-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89027-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: 2019-01/txt/msg03419.txt.bz2
Content-length: 716

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89027

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2019-1-24
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
      Known to work|                            |8.2.0
   Target Milestone|---                         |9.0
      Known to fail|                            |9.0

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Confirmed, started with r268067.
>From gcc-bugs-return-630611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:16:36 2019
Return-Path: <gcc-bugs-return-630611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8482 invoked by alias); 24 Jan 2019 08:16:36 -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 8403 invoked by uid 48); 24 Jan 2019 08:16:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89010] Update URLs in libsanitizer/README.gcc
Date: Thu, 24 Jan 2019 08:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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_status resolution
Message-ID: <bug-89010-4-AxPvHlnYzC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89010-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: 2019-01/txt/msg03420.txt.bz2
Content-length: 435

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89010

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #5 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Closing.
>From gcc-bugs-return-630612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:19:02 2019
Return-Path: <gcc-bugs-return-630612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13443 invoked by alias); 24 Jan 2019 08:19:01 -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 13386 invoked by uid 48); 24 Jan 2019 08:18:57 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89015] [9 Regression] ICE in lookup_decl_in_outer_ctx, at omp-low.c:3480
Date: Thu, 24 Jan 2019 08:19: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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: keywords bug_status cf_reconfirmed_on cc everconfirmed cf_known_to_fail
Message-ID: <bug-89015-4-nNbmEfjGr4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89015-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: 2019-01/txt/msg03421.txt.bz2
Content-length: 790

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89015

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-24
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1
      Known to fail|                            |9.0

--- Comment #2 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Started with r265930, rejected with GCC 8.
>From gcc-bugs-return-630613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:23:41 2019
Return-Path: <gcc-bugs-return-630613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18670 invoked by alias); 24 Jan 2019 08:23:40 -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 18558 invoked by uid 48); 24 Jan 2019 08:23:35 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89002] [7/8/9 Regression] ICE in scan_omp_1_op, at omp-low.c:3166
Date: Thu, 24 Jan 2019 08:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-89002-4-FIA0eH8ys3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89002-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89002-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: 2019-01/txt/msg03422.txt.bz2
Content-length: 649

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89002

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-24
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Started with r228777.
>From gcc-bugs-return-630614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:28:16 2019
Return-Path: <gcc-bugs-return-630614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25922 invoked by alias); 24 Jan 2019 08:28:15 -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 25681 invoked by uid 55); 24 Jan 2019 08:28:11 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Thu, 24 Jan 2019 08:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88994-4-RyhcgTmHBG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03423.txt.bz2
Content-length: 746

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88994

--- Comment #7 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Thu Jan 24 08:27:39 2019
New Revision: 268233

URL: https://gcc.gnu.org/viewcvs?rev=268233&root=gcc&view=rev
Log:
Fix broken filename for .gcda files starting with '..' (PR gcov-profile/88994).

2019-01-24  Martin Liska  <mliska@suse.cz>

        PR gcov-profile/88994
        * gcov-io.c (mangle_path): Do not allocate a bigger buffer,
        result will be always smaller or equal to the original.
        * gcov.c (mangle_name): Fix else branch where we should
        also copy to PTR and shift the pointer.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/gcov-io.c
    trunk/gcc/gcov.c
>From gcc-bugs-return-630615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:52:53 2019
Return-Path: <gcc-bugs-return-630615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15355 invoked by alias); 24 Jan 2019 08:52:53 -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 15267 invoked by uid 55); 24 Jan 2019 08:52:49 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Thu, 24 Jan 2019 08:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-piS8G6BaqQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03424.txt.bz2
Content-length: 876

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713

--- Comment #51 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 24 Jan 2019, tkoenig at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #49 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> (In reply to UroÅ¡ Bizjak from comment #48)
> > (In reply to rguenther@suse.de from comment #47)
> > > >But why don't we generate sqrtps for vector sqrtf?
> > > 
> > > That's the default for - mrecip back in time we benchmarked it and scalar
> > > recip miscompares sth.
> > 
> > It was polyhedron benchmark, in one benchmark, the index was calculated from
> > square root, and that was too sensitive for 2 ULP difference.
> 
> Argh.  Sacrificing performance for the sake of bugware...

Maybe use of FMA can recover 1 ULP and the benchmark ;)
>From gcc-bugs-return-630616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 08:53:59 2019
Return-Path: <gcc-bugs-return-630616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23109 invoked by alias); 24 Jan 2019 08:53:58 -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 20929 invoked by uid 48); 24 Jan 2019 08:53:54 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/88994] [GCOV] encoding (or unicode) error with gcov/gcc9 when generating filename
Date: Thu, 24 Jan 2019 08:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88994-4-JjwGSwp7Fy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88994-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: 2019-01/txt/msg03425.txt.bz2
Content-length: 433

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88994

Martin LiÅ¡ka <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-630618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:01:34 2019
Return-Path: <gcc-bugs-return-630618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86814 invoked by alias); 24 Jan 2019 09:01:34 -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 86264 invoked by uid 48); 24 Jan 2019 09:01:28 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/89000] gcov --function-summaries says No branches/No calls, only the File summary is correct
Date: Thu, 24 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89000-4-EwkTIZu1q3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89000-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89000-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: 2019-01/txt/msg03427.txt.bz2
Content-length: 858

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89000

--- Comment #3 from Martin LiÅ¡ka <marxin at gcc dot gnu.org> ---
> 
> We downgraded our toolchain to 7.4 because our process currently expects the
> gcov output to be consistent with previous output from our heritage
> baseline. We do need the output, and ideally it would be part of the -f
> option as in the past, but we could pull the data from the intermediate
> format, as you suggested, so once that is available we would be interested
> in reviewing it for adoption into our process and tools. Thanks for your
> quick response.

I would definitely recommend the intermediate format that will be reworked in
GCC 9.1 release. It should provide more stable format in a JSON format. Please
take a look:
https://gcc.gnu.org/onlinedocs/gcc/Invoking-Gcov.html#Invoking-Gcov
(--json-format).
>From gcc-bugs-return-630617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:01:30 2019
Return-Path: <gcc-bugs-return-630617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86284 invoked by alias); 24 Jan 2019 09:01:29 -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 86222 invoked by uid 48); 24 Jan 2019 09:01:25 -0000
From: "porton at narod dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89031] New: Should not report unused result when explicitly cast to void
Date: Thu, 24 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: porton at narod dot ru
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89031-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: 2019-01/txt/msg03426.txt.bz2
Content-length: 1060

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89031

            Bug ID: 89031
           Summary: Should not report unused result when explicitly cast
                    to void
           Product: gcc
           Version: 8.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: porton at narod dot ru
  Target Milestone: ---

GCC reports unused result even when explicitly converted to void to show the
developer's intent not to report a warning.

lib.c: In function â€˜libcomcom_run_commandâ€™:
lib.c:263:15: error: ignoring return value of â€˜writeâ€™, declared with attribute
warn_unused_result [-Werror=unused-result]
         (void)write(process.child[WRITE_END], &errno, sizeof(errno)); /*
deliberately don't check error */
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors

Should not report unused result when explicitly cast to void.
>From gcc-bugs-return-630619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:06:24 2019
Return-Path: <gcc-bugs-return-630619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99991 invoked by alias); 24 Jan 2019 09:06:23 -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 99875 invoked by uid 48); 24 Jan 2019 09:06:19 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/89032] New: Missing documentation for GCC 7.4.0
Date: Thu, 24 Jan 2019 09:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-89032-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: 2019-01/txt/msg03428.txt.bz2
Content-length: 514

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89032

            Bug ID: 89032
           Summary: Missing documentation for GCC 7.4.0
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
  Target Milestone: ---

Following url (mentioned https://gcc.gnu.org/gcc-7/) is missing:
https://gcc.gnu.org/onlinedocs/7.4.0/
>From gcc-bugs-return-630621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:07:48 2019
Return-Path: <gcc-bugs-return-630621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102395 invoked by alias); 24 Jan 2019 09:07:48 -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 102313 invoked by uid 48); 24 Jan 2019 09:07:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89015] [9 Regression] ICE in lookup_decl_in_outer_ctx, at omp-low.c:3480
Date: Thu, 24 Jan 2019 09:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component target_milestone
Message-ID: <bug-89015-4-wIYDplYNlr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89015-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: 2019-01/txt/msg03430.txt.bz2
Content-length: 409

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89015

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |openmp
          Component|c                           |middle-end
   Target Milestone|---                         |9.0
>From gcc-bugs-return-630620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:07:39 2019
Return-Path: <gcc-bugs-return-630620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101653 invoked by alias); 24 Jan 2019 09:07: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 101570 invoked by uid 48); 24 Jan 2019 09:07:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89027] [9 Regression] ICE: verify_gimple failed (Error: non-trivial conversion at assignment)
Date: Thu, 24 Jan 2019 09:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to everconfirmed
Message-ID: <bug-89027-4-zOsf7pTgmU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89027-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89027-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: 2019-01/txt/msg03429.txt.bz2
Content-length: 1014

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89027

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |jakub at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
-mvsx isn't needed, ICEs on x86_64 with those options too.
The problem is that shrink_simd_arrays shrinks the array types of the magic
simd array variables, but the code doesn't expect that there is anything
refering to the whole arrays; until recently that has been the case, now there
can be CLOBBERs that would need adjustment, but shrink_simd_arrays doesn't
really walk the whole IL so that it would be easy to find them and fix them. 
Guess easiest would be not to add clobbers for the simd array variables.
>From gcc-bugs-return-630622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:10:42 2019
Return-Path: <gcc-bugs-return-630622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106532 invoked by alias); 24 Jan 2019 09:10:42 -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 106476 invoked by uid 48); 24 Jan 2019 09:10:38 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89031] Should not report unused result when explicitly cast to void
Date: Thu, 24 Jan 2019 09:10: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89031-4-ojZ0asbmNI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89031-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89031-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: 2019-01/txt/msg03431.txt.bz2
Content-length: 226

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89031

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This attribute is documented this way.  I know there are a few duplicates of
this bug already filed too.
>From gcc-bugs-return-630623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:12:56 2019
Return-Path: <gcc-bugs-return-630623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24825 invoked by alias); 24 Jan 2019 09:12:55 -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 24732 invoked by uid 48); 24 Jan 2019 09:12:52 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Thu, 24 Jan 2019 09:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-veKrdIRGB4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03432.txt.bz2
Content-length: 438

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713

--- Comment #52 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #49)
> Argh.  Sacrificing performance for the sake of bugware...

But note that in this PR (specifically for avx512 vectors on this cpu), the OP
says that the recip version is slower than calling directly the right insn (it
wasn't clear if that was for inverse or for sqrt).
>From gcc-bugs-return-630624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:14:34 2019
Return-Path: <gcc-bugs-return-630624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29886 invoked by alias); 24 Jan 2019 09:14:33 -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 29830 invoked by uid 48); 24 Jan 2019 09:14:29 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89018] common subexpression present in both branches of condition is not factored out
Date: Thu, 24 Jan 2019 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-89018-4-nw9qJrPuwE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89018-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89018-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: 2019-01/txt/msg03433.txt.bz2
Content-length: 1839

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89018

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-24
                 CC|                            |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
fold does/did some of these transforms (not for the call case).  There's
tail merging on GIMPLE and cross-jumping on RTL as well as ifcvt/phiopt
that in theory could handle all cases.

There's also code sinking that could be massaged (like I massaged it
to common stores).  It doesn't really fit very well anywhere though
(phiopt comes closest I think, as "pre"-pass to the other transforms,
emptying the middle blocks as much as possible).

  <bb 2> [local count: 1073741824]:
  if (a_2(D) >= b_3(D))
    goto <bb 3>; [50.00%]
  else
    goto <bb 4>; [50.00%]

  <bb 3> [local count: 536870913]:
  iftmp.0_4 = -a_2(D);
  goto <bb 5>; [100.00%]

  <bb 4> [local count: 536870913]:
  iftmp.0_5 = -b_3(D);

  <bb 5> [local count: 1073741824]:
  # iftmp.0_1 = PHI <iftmp.0_4(3), iftmp.0_5(4)>
  return iftmp.0_1;

..

  <bb 2> [local count: 1073741824]:
  if (a_3(D) >= b_4(D))
    goto <bb 3>; [50.00%]
  else
    goto <bb 4>; [50.00%]

  <bb 3> [local count: 536870913]:
  iftmp.2_7 = transform (a_3(D));
  goto <bb 5>; [100.00%]

  <bb 4> [local count: 536870913]:
  iftmp.2_9 = transform (b_4(D));

  <bb 5> [local count: 1073741824]:
  # iftmp.2_1 = PHI <iftmp.2_7(3), iftmp.2_9(4)>
  return iftmp.2_1;
>From gcc-bugs-return-630625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:16:41 2019
Return-Path: <gcc-bugs-return-630625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34057 invoked by alias); 24 Jan 2019 09:16:39 -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 33971 invoked by uid 55); 24 Jan 2019 09:16:35 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Thu, 24 Jan 2019 09:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: REOPENED
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:
Message-ID: <bug-88713-4-nLQhKRSr5z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-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: 2019-01/txt/msg03434.txt.bz2
Content-length: 847

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713

--- Comment #53 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 24 Jan 2019, glisse at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
> 
> --- Comment #52 from Marc Glisse <glisse at gcc dot gnu.org> ---
> (In reply to Thomas Koenig from comment #49)
> > Argh.  Sacrificing performance for the sake of bugware...
> 
> But note that in this PR (specifically for avx512 vectors on this cpu), the OP
> says that the recip version is slower than calling directly the right insn (it
> wasn't clear if that was for inverse or for sqrt).

Probably depends on the microarchitecture, yes.  But I'd fully
expect the two-NR step variant to be slower for a sensible
HW implementation (even more so if we need to fend off the
exceptional cases)
>From gcc-bugs-return-630626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:19:02 2019
Return-Path: <gcc-bugs-return-630626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51975 invoked by alias); 24 Jan 2019 09:19:02 -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 49663 invoked by uid 48); 24 Jan 2019 09:18:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89021] Implement mmintrin.h in SSE
Date: Thu, 24 Jan 2019 09:19: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-89021-4-iSb7tHKe0g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89021-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89021-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: 2019-01/txt/msg03435.txt.bz2
Content-length: 343

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89021

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think that to avoid surprises -mno-mmx should be the default on x86 and thus
MMX code would need to explicitely supply -mmmx.  Would that work around the
issue or would we see odd errors when using the mm intrinsics?
>From gcc-bugs-return-630627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:19:51 2019
Return-Path: <gcc-bugs-return-630627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96321 invoked by alias); 24 Jan 2019 09:19:51 -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 91880 invoked by uid 48); 24 Jan 2019 09:19:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89024] [7/8/9 Regression] ICE testing convertibility of incomplete enumeration types
Date: Thu, 24 Jan 2019 09:19: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-89024-4-nU06gN1MgY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89024-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: 2019-01/txt/msg03436.txt.bz2
Content-length: 292

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89024

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
>From gcc-bugs-return-630628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:21:06 2019
Return-Path: <gcc-bugs-return-630628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31703 invoked by alias); 24 Jan 2019 09:21:05 -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 28460 invoked by uid 48); 24 Jan 2019 09:21:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89027] [9 Regression] ICE: verify_gimple failed (Error: non-trivial conversion at assignment)
Date: Thu, 24 Jan 2019 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-89027-4-LVKMIAlUdr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89027-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89027-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: 2019-01/txt/msg03437.txt.bz2
Content-length: 292

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89027

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
>From gcc-bugs-return-630629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:22:51 2019
Return-Path: <gcc-bugs-return-630629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108815 invoked by alias); 24 Jan 2019 09:22: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 108746 invoked by uid 48); 24 Jan 2019 09:22:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/37804] friend declaration leaks into global scope at template instantiation
Date: Thu, 24 Jan 2019 09:22: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.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: keywords cf_gcctarget cf_reconfirmed_on cf_gcchost cf_gccbuild
Message-ID: <bug-37804-4-gS0cJKJW5p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37804-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: 2019-01/txt/msg03438.txt.bz2
Content-length: 722

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37804

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|rejects-valid               |
             Target|x86_64-linux-gnu            |
   Last reconfirmed|2008-10-11 13:07:05         |2019-1-24
               Host|x86_64-linux-gnu            |
              Build|x86_64-linux-gnu            |

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The cases in comment 6 and comment 8 are a different bug (PR 59930) which was
fixed for gcc 8.

The original accepts-invalid bug is still present on trunk.
>From gcc-bugs-return-630630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:28:44 2019
Return-Path: <gcc-bugs-return-630630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33958 invoked by alias); 24 Jan 2019 09:28:43 -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 30631 invoked by uid 48); 24 Jan 2019 09:28:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89028] 8-byte loop isn't vectorized
Date: Thu, 24 Jan 2019 09:28: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: cf_gcctarget bug_status cf_reconfirmed_on blocked everconfirmed
Message-ID: <bug-89028-4-g6uF6jehc4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89028-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89028-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: 2019-01/txt/msg03439.txt.bz2
Content-length: 2091

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89028

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86_64-*-* i?86-*-*
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2019-01-24
             Blocks|                            |53947
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Of course we do not vectorize at -O2.  At -O3 the issue is the target doesn't
advertise word_mode as vector size to use and the vectorizer doesn't support
vectorization using half of a vector.

If you'd do

Index: gcc/config/i386/i386.c
===================================================================
--- gcc/config/i386/i386.c      (revision 268010)
+++ gcc/config/i386/i386.c      (working copy)
@@ -50153,6 +50153,11 @@ ix86_autovectorize_vector_sizes (vector_
       sizes->safe_push (32);
       sizes->safe_push (16);
     }
+  else
+    {
+      sizes->safe_push (16);
+      sizes->safe_push (8);
+    }
 }

 /* Implemenation of targetm.vectorize.get_mask_mode.  */

you get vectorization using DImode regs:

rsqrt:
.LFB0:
        .cfi_startproc
        movabsq $9187201950435737471, %rdx
        movq    (%rdi), %rax
        movq    (%rsi), %rsi
        movq    %rdx, %rcx
        andq    %rax, %rcx
        andq    %rsi, %rdx
        xorq    %rsi, %rax
        addq    %rcx, %rdx
        movabsq $-9187201950435737472, %rcx
        andq    %rcx, %rax
        xorq    %rdx, %rax
        movq    %rax, (%rdi)
        ret

not exactly what you wanted I guess ;)  Anything else would require
vectorizer adjustments.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
>From gcc-bugs-return-630631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:30:02 2019
Return-Path: <gcc-bugs-return-630631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35677 invoked by alias); 24 Jan 2019 09:30:01 -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 35567 invoked by uid 48); 24 Jan 2019 09:29:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89029] __builtin_constant_p erroneously true
Date: Thu, 24 Jan 2019 09:30: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
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: bug_status resolution
Message-ID: <bug-89029-4-ABc6RKPzev@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89029-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89029-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: 2019-01/txt/msg03440.txt.bz2
Content-length: 428

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89029

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yes
>From gcc-bugs-return-630632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 24 09:31:45 2019
Return-Path: <gcc-bugs-return-630632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41667 invoked by alias); 24 Jan 2019 09:31:44 -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 41560 invoked by uid 89); 24 Jan 2019 09:31:44 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=4.8 required=5.0 testsºD_OUTLOOK_FROM,BAYES_50,FREEMAIL_FROM autolearn=no version=3.3.2 spammy=WeChat, H*Ad:D*outlook.com, H*r:sk:bounce-, HX-Envelope-From:sk:bounce-
X-HELO: mk-cc.xyz
Received: from Unknown (HELO mk-cc.xyz) (114.67.29.253) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 24 Jan 2019 09:31:43 +0000
Received: by mk-cc.xyz id h962vo0e97cn for <gcc-bugs@gcc.gnu.org>; Thu, 24 Jan 2019 17:31:28 +0800 (envelope-from <bounce-656-1318088-452-248@mk-cc.xyz>)
Date: Thu, 24 Jan 2019 09:31:00 -0000
Return-Path: bounce-656-1318088-452-248@mk-cc.xyz
To: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
From: Corey <Corey.xysky@outlook.com>
Reply-to: Corey <Corey.xysky@outlook.com>
Subject: =?utf-8?Q?Re:Â NEWÂ ORDERÂ OFÂ 24/01/2019.?Message-ID: <6c068a9a70629e396e912476e231bd16@10.13.77.248>
X-MessageID: M3x8fHw2NDYxfHx8fGdjYy1idWdzQGdjYy5nbnUub3JnfHx8fDJ8fHx8MXx8fHww
X-Report-Abuse: <http://114.67.29.253/oem/report_abuse.php?mid=M3x8fHw2NDYxfHx8fGdjYy1idWdzQGdjYy5nbnUub3JnfHx8fDJ8fHx8MXx8fHww>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-SW-Source: 2019-01/txt/msg03441.txt.bz2
Content-length: 113

Can we order small quantity for our first order?

Regards,
WeChat: Corey_Xy_91
mailbox: Corey.xysky@outlook.com


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators
  2019-01-18 17:12 [Bug target/88916] New: [x86] suboptimal code generated for integer comparisons joined with boolean operators wojciech_mula at poczta dot onet.pl
@ 2021-08-11  5:19 ` pinskia at gcc dot gnu.org
  2022-11-27  6:39 ` pinskia at gcc dot gnu.org
  2022-11-27  6:52 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-08-11  5:19 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu.org
           Severity|normal                      |enhancement

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators
  2019-01-18 17:12 [Bug target/88916] New: [x86] suboptimal code generated for integer comparisons joined with boolean operators wojciech_mula at poczta dot onet.pl
  2021-08-11  5:19 ` [Bug tree-optimization/88916] " pinskia at gcc dot gnu.org
@ 2022-11-27  6:39 ` pinskia at gcc dot gnu.org
  2022-11-27  6:52 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-11-27  6:39 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |13.0

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
both_nonnegative looks to be fixed:

        movq    %rdi, %rax
        orq     %rsi, %rax
        notq    %rax
        shrq    $63, %rax
        ret

  _8 = a_4(D) | b_5(D);
  _9 = _8 >= 0;
  _6 = (int) _9;

different_sign also seems to be fixed:
        .cfi_startproc
        xorq    %rsi, %rdi
        shrq    $63, %rdi
        movq    %rdi, %rax
        ret
  _6 = a_2(D) ^ b_3(D);
  _1 = _6 < 0;

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug tree-optimization/88916] [x86] suboptimal code generated for integer comparisons joined with boolean operators
  2019-01-18 17:12 [Bug target/88916] New: [x86] suboptimal code generated for integer comparisons joined with boolean operators wojciech_mula at poczta dot onet.pl
  2021-08-11  5:19 ` [Bug tree-optimization/88916] " pinskia at gcc dot gnu.org
  2022-11-27  6:39 ` pinskia at gcc dot gnu.org
@ 2022-11-27  6:52 ` pinskia at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-11-27  6:52 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88916

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=96681,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=95731
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |11.0

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
different_sign was fixed by r11-6738-g5c046034e3ea61 (aka PR 96681)

both_nonnegative was fixed by  r11-6609-g13d47c37a2c043f3e598 (aka PR 95731)


So closing as fixed.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-11-27  6:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-18 17:12 [Bug target/88916] New: [x86] suboptimal code generated for integer comparisons joined with boolean operators wojciech_mula at poczta dot onet.pl
2021-08-11  5:19 ` [Bug tree-optimization/88916] " pinskia at gcc dot gnu.org
2022-11-27  6:39 ` pinskia at gcc dot gnu.org
2022-11-27  6:52 ` pinskia at gcc dot gnu.org

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).