public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
[not found] <bug-86005-4@http.gcc.gnu.org/bugzilla/>
@ 2018-05-31 5:53 ` andrew at sifive dot com
2023-07-07 16:22 ` patrick at rivosinc dot com
1 sibling, 0 replies; 2+ messages in thread
From: andrew at sifive dot com @ 2018-05-31 5:53 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: 288569 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #2 from Andrew Waterman <andrew at sifive dot com> ---
I realize the documentation doesn't concur with me, but as long as gcc
and libgcc agree on the lock-freeness of the routines, I don't see the
harm. (wrt. rv32ia, at least.)
On Wed, May 30, 2018 at 10:40 PM, asb at lowrisc dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
>
> Alex Bradbury <asb at lowrisc dot org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |asb at lowrisc dot org
> Summary|[RISCV] Invalid lowering of |[RISCV] Invalid intermixing
> |atomics for -march=rv32i / |of __atomic_* libcalls and
> |-march=rv64i |inline atomic instruction
> | |sequences
>
> --- Comment #1 from Alex Bradbury <asb at lowrisc dot org> ---
> Actually I think this bug is wider in scope than I first thought. GCC will also
> intermix __atomic libcalls and inline instruction sequences with -march=rv32ia
> when values less than XLEN in size are accessed.
>
> $ cat foo.c
> char atomic(char *i) {
> char j = __atomic_add_fetch(i, 1, __ATOMIC_SEQ_CST);
> char k;
> __atomic_load(i, &k, __ATOMIC_SEQ_CST);
> return j+k;
> }
>
> $ ./riscv32-unknown-elf-gcc -march=rv32ia foo.c -O1 -S -o -
> .file "foo.c"
> .option nopic
> .text
> .align 2
> .globl atomic
> .type atomic, @function
> atomic:
> addi sp,sp,-16
> sw ra,12(sp)
> sw s0,8(sp)
> mv s0,a0
> li a2,5
> li a1,1
> call __atomic_fetch_add_1
> addi a0,a0,1
> andi a0,a0,0xff
> fence iorw,iorw
> lbu a5,0(s0)
> fence iorw,iorw
> add a0,a0,a5
> andi a0,a0,0xff
> lw ra,12(sp)
> lw s0,8(sp)
> addi sp,sp,16
> jr ra
> .size atomic, .-atomic
> .ident "GCC: (GNU) 9.0.0 20180530 (experimental)"
>From gcc-bugs-return-606130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 06:07:48 2018
Return-Path: <gcc-bugs-return-606130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22726 invoked by alias); 31 May 2018 06: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 22669 invoked by uid 48); 31 May 2018 06:07:44 -0000
From: "asb at lowrisc dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
Date: Thu, 31 May 2018 06: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asb at lowrisc 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-86005-4-5I6KYgOWQK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03025.txt.bz2
Content-length: 614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #3 from Alex Bradbury <asb at lowrisc dot org> ---
(In reply to Andrew Waterman from comment #2)
> I realize the documentation doesn't concur with me, but as long as gcc
> and libgcc agree on the lock-freeness of the routines, I don't see the
> harm. (wrt. rv32ia, at least.)
Yes, for RV32IA it might be allowable - assuming you're able for the compiler
to make the assumption that it knows that property of the __atomic_*
implementation and that assumption won't/can't be invalidated by linking in
another implementation which isn't lock-free.
>From gcc-bugs-return-606131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 07:25:21 2018
Return-Path: <gcc-bugs-return-606131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53680 invoked by alias); 31 May 2018 07:25: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 50433 invoked by uid 48); 31 May 2018 07:25:16 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85591] __builtin_cpu_is() is not detecting bdver2 with Model = 0x02
Date: Thu, 31 May 2018 07: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: 8.0.1
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: attachments.created
Message-ID: <bug-85591-4-1PKZwwvzUS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03026.txt.bz2
Content-length: 282
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 44218
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44218&action=edit
Proposed patch
Can someone please test the attached patch?
>From gcc-bugs-return-606132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 08:58:06 2018
Return-Path: <gcc-bugs-return-606132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76530 invoked by alias); 31 May 2018 08: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 76172 invoked by uid 48); 31 May 2018 08:58:01 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86012] New: [7/8/9 Regression] libsanitizer build failure on sparc64-linux-gnu
Date: Thu, 31 May 2018 08: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: doko 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-86012-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03027.txt.bz2
Content-length: 1221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86012
Bug ID: 86012
Summary: [7/8/9 Regression] libsanitizer build failure on
sparc64-linux-gnu
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
The fix for PR85835 causes the build to fail on sparc64-linux-gnu in the 32bit
multilib.
../../../../../src/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:262:2:
error: #error Unknown size of struct ustat
#error Unknown size of struct ustat
^~~~~
../../../../../src/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:264:30:
error: 'SIZEOF_STRUCT_USTAT' was not declared in this scope
unsigned struct_ustat_sz = SIZEOF_STRUCT_USTAT;
^~~~~~~~~~~~~~~~~~~
make[10]: *** [Makefile:539: sanitizer_platform_limits_posix.lo] Error 1
make[10]: Leaving directory
'/<<PKGBUILDDIR>>/build/sparc64-linux-gnu/32/libsanitizer/sanitizer_common'
make[9]: *** [Makefile:472: all-recursive] Error 1
>From gcc-bugs-return-606133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 09:01:11 2018
Return-Path: <gcc-bugs-return-606133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97979 invoked by alias); 31 May 2018 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 97728 invoked by uid 48); 31 May 2018 09:01:02 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85835] libsanitizer includes <sys/ustat.h> unconditionally
Date: Thu, 31 May 2018 09: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: doko 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-85835-4-oQLPJvvum1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03028.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85835
Matthias Klose <doko at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |doko at gcc dot gnu.org
--- Comment #8 from Matthias Klose <doko at gcc dot gnu.org> ---
see PR86012 for a build failure on sparc64.
>From gcc-bugs-return-606134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 09:48:59 2018
Return-Path: <gcc-bugs-return-606134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27593 invoked by alias); 31 May 2018 09:48: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 15683 invoked by uid 48); 31 May 2018 09:48:24 -0000
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86013] New: std::vector::shrink_to_fit() could sometimes use realloc()
Date: Thu, 31 May 2018 09:48: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jan.kratochvil 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-86013-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03029.txt.bz2
Content-length: 797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86013
Bug ID: 86013
Summary: std::vector::shrink_to_fit() could sometimes use
realloc()
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: jan.kratochvil at redhat dot com
Target Milestone: ---
std::vector::shrink_to_fit() when reducing the size it still calls new()+copy.
It could use realloc() when the objects are trivially copyable resulting in no
copy during size reduction.
Maybe it could even always call realloc() for size reduction of any type of
objects and just assert the returned pointer did not change.
>From gcc-bugs-return-606135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 09:58:11 2018
Return-Path: <gcc-bugs-return-606135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46655 invoked by alias); 31 May 2018 09: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 46527 invoked by uid 55); 31 May 2018 09:58:07 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86012] [7/8/9 Regression] libsanitizer build failure on sparc64-linux-gnu
Date: Thu, 31 May 2018 09:58: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: doko 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-86012-4-IVrYIRWbdJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03030.txt.bz2
Content-length: 566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86012
--- Comment #1 from Matthias Klose <doko at gcc dot gnu.org> ---
Author: doko
Date: Thu May 31 09:57:33 2018
New Revision: 260990
URL: https://gcc.gnu.org/viewcvs?rev=260990&root=gcc&view=rev
Log:
2018-05-31 Matthias Klose <doko@ubuntu.com>
PR sanitizer/86012
* sanitizer_common/sanitizer_platform_limits_posix.cc: Define
SIZEOF_STRUCT_USTAT for 32bit sparc.
Modified:
trunk/libsanitizer/ChangeLog
trunk/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
>From gcc-bugs-return-606136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 09:59:09 2018
Return-Path: <gcc-bugs-return-606136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48562 invoked by alias); 31 May 2018 09:59: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 48451 invoked by uid 55); 31 May 2018 09:59:04 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86012] [7/8/9 Regression] libsanitizer build failure on sparc64-linux-gnu
Date: Thu, 31 May 2018 09:59: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: doko 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-86012-4-gT6oNhpDiR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03031.txt.bz2
Content-length: 606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86012
--- Comment #2 from Matthias Klose <doko at gcc dot gnu.org> ---
Author: doko
Date: Thu May 31 09:58:32 2018
New Revision: 260991
URL: https://gcc.gnu.org/viewcvs?rev=260991&root=gcc&view=rev
Log:
2018-05-31 Matthias Klose <doko@ubuntu.com>
PR sanitizer/86012
* sanitizer_common/sanitizer_platform_limits_posix.cc: Define
SIZEOF_STRUCT_USTAT for 32bit sparc.
Modified:
branches/gcc-8-branch/libsanitizer/ChangeLog
branches/gcc-8-branch/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
>From gcc-bugs-return-606137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:01:06 2018
Return-Path: <gcc-bugs-return-606137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51650 invoked by alias); 31 May 2018 10: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 51429 invoked by uid 55); 31 May 2018 10:00:57 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86012] [7/8/9 Regression] libsanitizer build failure on sparc64-linux-gnu
Date: Thu, 31 May 2018 10: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: doko 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-86012-4-mylCFLRF5P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03032.txt.bz2
Content-length: 606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86012
--- Comment #3 from Matthias Klose <doko at gcc dot gnu.org> ---
Author: doko
Date: Thu May 31 09:59:35 2018
New Revision: 260992
URL: https://gcc.gnu.org/viewcvs?rev=260992&root=gcc&view=rev
Log:
2018-05-31 Matthias Klose <doko@ubuntu.com>
PR sanitizer/86012
* sanitizer_common/sanitizer_platform_limits_posix.cc: Define
SIZEOF_STRUCT_USTAT for 32bit sparc.
Modified:
branches/gcc-7-branch/libsanitizer/ChangeLog
branches/gcc-7-branch/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
>From gcc-bugs-return-606138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:22:26 2018
Return-Path: <gcc-bugs-return-606138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1357 invoked by alias); 31 May 2018 10:22: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 1290 invoked by uid 48); 31 May 2018 10:22:22 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86014] New: [AArch64] missed LDP optimization
Date: Thu, 31 May 2018 10:22: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: clyon 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-86014-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03033.txt.bz2
Content-length: 1364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86014
Bug ID: 86014
Summary: [AArch64] missed LDP optimization
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
After r260952 (Improve LDP/STP generation that requires a base register),
I noticed that the new test ldp_stp_10.c fails in ILP32 mode:
FAIL: gcc.target/aarch64/ldp_stp_10.c scan-assembler-times
ldp\tw[0-9]+, w[0-9]+, 2
FAIL: gcc.target/aarch64/ldp_stp_10.c scan-assembler-times
ldp\tx[0-9]+, x[0-9]+, 2
Kyrill thinks it's a missed-optimization:
This is because the register allocation is such that the last load in the
sequence clobbers the address register like so:
...
ldr w0, [x2, 1600]
ldr w1, [x2, 2108]
ldr w3, [x2, 1604]
ldr w2, [x2, 2112] //<<--- x2 is an address and a destination
...
The checks in aarch64_operands_adjust_ok_for_ldpstp bail out for this case.
I believe as long as w2 is loaded in the second/last LDP pair that this
optimisation generates
and the address is not a writeback address (as we are guaranteed in this
context) then it should
be safe to form the LDP pairs.
>From gcc-bugs-return-606139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:23:18 2018
Return-Path: <gcc-bugs-return-606139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2841 invoked by alias); 31 May 2018 10:23: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 2783 invoked by uid 48); 31 May 2018 10:23:14 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86014] [AArch64] missed LDP optimization
Date: Thu, 31 May 2018 10: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: 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 everconfirmed
Message-ID: <bug-86014-4-1bzQj2fR2Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86014-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03034.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86014
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-31
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed.
>From gcc-bugs-return-606140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:24:00 2018
Return-Path: <gcc-bugs-return-606140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8698 invoked by alias); 31 May 2018 10:24: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 8629 invoked by uid 48); 31 May 2018 10:23:56 -0000
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86012] [7/8/9 Regression] libsanitizer build failure on sparc64-linux-gnu
Date: Thu, 31 May 2018 10:24: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: doko 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-86012-4-r8136mg4MI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86012-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03035.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86012
Matthias Klose <doko at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Matthias Klose <doko at gcc dot gnu.org> ---
fixed.
>From gcc-bugs-return-606141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:37:43 2018
Return-Path: <gcc-bugs-return-606141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73168 invoked by alias); 31 May 2018 10:37: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 73129 invoked by uid 48); 31 May 2018 10:37:36 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82089] emit_cstore sign-extends BImode result for STORE_FLAG_VALUE == 1
Date: Thu, 31 May 2018 10: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: wrong-code
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-82089-4-lUks25Mllt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03036.txt.bz2
Content-length: 591
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82089
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Andrew Stubbs from comment #5)
> Any reason not to get this committed?
No, this should get committed.
This should either:
- be fixed as part of upstreaming the gcn port, or
- we can trigger the problem on bfin using the afore-mentioned trigger patch,
and test that in combination with the fix, and prove that there are no
regressions compared a vanilla bfin build and test, and see it this level
of testing is acceptable for a middle-end maintainer.
>From gcc-bugs-return-606142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:49:02 2018
Return-Path: <gcc-bugs-return-606142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109158 invoked by alias); 31 May 2018 10:49: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 105931 invoked by uid 48); 31 May 2018 10:48:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86013] std::vector::shrink_to_fit() could sometimes use realloc()
Date: Thu, 31 May 2018 10: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.1.1
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-86013-4-xeJJHBnPgh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03037.txt.bz2
Content-length: 920
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86013
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jan Kratochvil from comment #0)
> std::vector::shrink_to_fit() when reducing the size it still calls
> new()+copy.
> It could use realloc() when the objects are trivially copyable resulting in
> no copy during size reduction.
In general it can't. It's only valid to do that when we know that the allocator
obtained memory from malloc, which we can't know for the default new_allocator
(users could have replaced operator new to get memory from somewhere else). It
would be OK for malloc_allocator only.
The only reliable way to get realloc-like behaviour is by extending the
allocator API to cover it.
> Maybe it could even always call realloc() for size reduction of any type of
> objects and just assert the returned pointer did not change.
That suggestion terrifies me.
>From gcc-bugs-return-606143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:57:31 2018
Return-Path: <gcc-bugs-return-606143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38652 invoked by alias); 31 May 2018 10: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 38612 invoked by uid 48); 31 May 2018 10:57:24 -0000
From: "stefantalpalaru at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85591] __builtin_cpu_is() is not detecting bdver2 with Model = 0x02
Date: Thu, 31 May 2018 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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stefantalpalaru at yahoo 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-85591-4-1V5ivXE0eq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03038.txt.bz2
Content-length: 206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
--- Comment #3 from Ștefan Talpalaru <stefantalpalaru at yahoo dot com> ---
I applied the patch to gcc-8.1.0 and it fixes the problem on my CPU.
>From gcc-bugs-return-606144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 10:59:09 2018
Return-Path: <gcc-bugs-return-606144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40036 invoked by alias); 31 May 2018 10:59: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 40010 invoked by uid 48); 31 May 2018 10:59:04 -0000
From: "stefantalpalaru at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/86007] precompiled header on bdver2 with -march=native triggers a "created and used with differing settings of '-mlwp'" warning, intermittently
Date: Thu, 31 May 2018 10:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: pch
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stefantalpalaru at yahoo 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-86007-4-EQweenUQyB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03039.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86007
--- Comment #1 from Ștefan Talpalaru <stefantalpalaru at yahoo dot com> ---
The patch that fixes #85591 doesn't fix this problem.
>From gcc-bugs-return-606145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 12:19:00 2018
Return-Path: <gcc-bugs-return-606145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117725 invoked by alias); 31 May 2018 12:19: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 117639 invoked by uid 55); 31 May 2018 12:18:54 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85951] make_signed and make_unsigned are incorrect for wchar_t, char16_t, and char32_t
Date: Thu, 31 May 2018 12: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: 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-85951-4-z0yIecYvzm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03040.txt.bz2
Content-length: 2504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85951
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 31 12:18:19 2018
New Revision: 261023
URL: https://gcc.gnu.org/viewcvs?rev=261023&root=gcc&view=rev
Log:
PR libstdc++/85951 for make_signed/make_unsigned for character types
Because the wide character types are neither signed integer types nor
unsigned integer types they need to be transformed to an integral type
of the correct size and the lowest rank (which is not necessarily the
underlying type). Reuse the helpers for enumeration types to select the
correct integer.
The refactoring of __make_unsigned_selector and __make_signed_selector
slightly reduces the number of template instantiations and so reduces
memory usage.
PR libstdc++/85951
* include/std/type_traits [_GLIBCXX_USE_C99_STDINT_TR1]: Do not define
uint_least16_t and uint_least32_t.
(__make_unsigned<wchar_t>): Define unconditionally.
(__make_unsigned_selector<_Tp, true, false>): Remove intermediate
typedefs.
(__make_unsigned_selector_base): New type to provide helper templates.
(__make_unsigned_selector<_Tp, false, true>): Reimplement using
__make_unsigned_selector_base helpers.
(__make_unsigned<char16_t>, __make_unsigned<char32_t>): Define.
(__make_signed_selector<_Tp, true, false>): Remove intermediate
typedefs.
(__make_signed<wchar_t>, __make_signed<char16_t>)
(__make_signed<char32_t>)): Define unconditionally.
* testsuite/20_util/make_signed/requirements/typedefs-3.cc: Check
wchar_t, char16_t and char32_t are transformed correctly.
* testsuite/20_util/make_signed/requirements/typedefs_neg.cc: Adjust
dg-error lineno.
* testsuite/20_util/make_unsigned/requirements/typedefs-3.cc: Check
wchar_t, char16_t and char32_t are transformed correctly.
* testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc: Adjust
dg-error lineno.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/std/type_traits
trunk/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs-3.cc
trunk/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs_neg.cc
trunk/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs-3.cc
trunk/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc
>From gcc-bugs-return-606146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:07:17 2018
Return-Path: <gcc-bugs-return-606146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84073 invoked by alias); 31 May 2018 13:07: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 83782 invoked by uid 48); 31 May 2018 13:07:11 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86006] compile time error generic type bound procedure
Date: Thu, 31 May 2018 13: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-86006-4-IhFRXsY9aN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86006-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86006-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03041.txt.bz2
Content-length: 872
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86006
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-31
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I get the error with at least 4.8 up to trunk (9.0).
> From my understanding this should work.
Where do you expect the ambiguity between
Class(*), Intent(Out), Pointer :: TSOut
and
Integer*8, Intent(In) :: ISPos
to be resolved?
> It also compiles without error with other compilers (e.g. ifort)
Did you use any option enforcing the compliance to some Fortran standard?
>From gcc-bugs-return-606147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:08:10 2018
Return-Path: <gcc-bugs-return-606147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87776 invoked by alias); 31 May 2018 13:08: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 87715 invoked by uid 48); 31 May 2018 13:08:05 -0000
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86013] std::vector::shrink_to_fit() could sometimes use realloc()
Date: Thu, 31 May 2018 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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jan.kratochvil 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-86013-4-kHJpQtjGfa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03042.txt.bz2
Content-length: 238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86013
--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
You apparently know better all the pitfalls, I just got shocked that a
squeezing shrink_to_fit() does a copy.
>From gcc-bugs-return-606148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:12:39 2018
Return-Path: <gcc-bugs-return-606148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94055 invoked by alias); 31 May 2018 13:12: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 94002 invoked by uid 48); 31 May 2018 13:12:35 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85982] ICE in resolve_component, at fortran/resolve.c:13696
Date: Thu, 31 May 2018 13:12: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-invalid-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: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-85982-4-WgPohaRJFv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85982-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03043.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85982
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-31
CC| |foreese at gcc dot gnu.org
Target Milestone|--- |6.5
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from 6.4.0 up to trunk (9.0).
>From gcc-bugs-return-606149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:15:53 2018
Return-Path: <gcc-bugs-return-606149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128055 invoked by alias); 31 May 2018 13:15: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 127934 invoked by uid 48); 31 May 2018 13:15:47 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85983] ICE in check_dtio_interface1, at fortran/interface.c:4748
Date: Thu, 31 May 2018 13:15: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: P4
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 cc everconfirmed
Message-ID: <bug-85983-4-sALzoBkapt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85983-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85983-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03044.txt.bz2
Content-length: 655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85983
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-31
CC| |jvdelisle at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from 7.3.0 up to trunk (9.0).
>From gcc-bugs-return-606150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:47:03 2018
Return-Path: <gcc-bugs-return-606150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21902 invoked by alias); 31 May 2018 13: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 18860 invoked by uid 48); 31 May 2018 13:46:58 -0000
From: "development at jordi dot vilar.cat" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85670] `std::filesystem` does not compile on mingw-w64
Date: Thu, 31 May 2018 13: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: development at jordi dot vilar.cat
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: cc
Message-ID: <bug-85670-4-52v16CWl9o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03045.txt.bz2
Content-length: 971
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85670
Jordi Vilar <development at jordi dot vilar.cat> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |development at jordi dot vilar.cat
--- Comment #4 from Jordi Vilar <development at jordi dot vilar.cat> ---
No only operator != is referenced (line 237) before it is declared (line 550).
Also __is_encoded_char is instantiated (line 412) before it is specialized
(line 511) via the constructor (line 180). In both cases, it only happens if
the _GLIBCXX_FILESYSTEM_IS_WINDOWS is defined. And finally, both overloads of
u8path must be introduced in the reversed order.
I managed to compile just #include <filesystem>, but then it fails with
<fstream> as it is not able to open file streams with a path object (it looks
like it lacks a constructor with const wchar_t*)
>From gcc-bugs-return-606151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:52:36 2018
Return-Path: <gcc-bugs-return-606151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52032 invoked by alias); 31 May 2018 13:52: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 51988 invoked by uid 48); 31 May 2018 13:52:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85254] boost::is_final does not work for template types
Date: Thu, 31 May 2018 13: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: 7.2.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
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:
Message-ID: <bug-85254-4-jgw9nTjVvy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85254-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85254-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03046.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85254
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I hoped this would fix it, but it didn't:
--- a/gcc/cp/semantics.c
+++ b/gcc/cp/semantics.c
@@ -9010,6 +9010,7 @@ trait_expr_value (cp_trait_kind kind, tree type1, tree
type2)
return type_code1 == ENUMERAL_TYPE;
case CPTK_IS_FINAL:
+ type1 = TYPE_MAIN_VARIANT (type1);
return CLASS_TYPE_P (type1) && CLASSTYPE_FINAL (type1);
case CPTK_IS_LITERAL_TYPE:
>From gcc-bugs-return-606152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 13:53:15 2018
Return-Path: <gcc-bugs-return-606152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54661 invoked by alias); 31 May 2018 13:53: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 54195 invoked by uid 48); 31 May 2018 13:53:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85670] `std::filesystem` does not compile on mingw-w64
Date: Thu, 31 May 2018 13:53: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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-85670-4-VLptaWPdAg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03047.txt.bz2
Content-length: 164
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85670
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
All those issues will be fixed later today.
>From gcc-bugs-return-606153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:08:01 2018
Return-Path: <gcc-bugs-return-606153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63147 invoked by alias); 31 May 2018 14:08: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 63061 invoked by uid 55); 31 May 2018 14:07:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85951] make_signed and make_unsigned are incorrect for wchar_t, char16_t, and char32_t
Date: Thu, 31 May 2018 14: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: 9.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-85951-4-XXFIpCXDEn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03048.txt.bz2
Content-length: 2068
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85951
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 31 14:07:22 2018
New Revision: 261024
URL: https://gcc.gnu.org/viewcvs?rev=261024&root=gcc&view=rev
Log:
PR libstdc++/85951 for make_signed/make_unsigned for character types
Because the wide character types are neither signed integer types nor
unsigned integer types they need to be transformed to an integral type
of the correct size and the lowest rank (which is not necessarily the
underlying type). Reuse the helpers for enumeration types to select the
correct integer.
PR libstdc++/85951
* include/std/type_traits [_GLIBCXX_USE_C99_STDINT_TR1]: Do not define
uint_least16_t and uint_least32_t.
(__make_unsigned<wchar_t>): Define unconditionally.
(__make_unsigned<char16_t>, __make_unsigned<char32_t>): Define.
(__make_signed<wchar_t>, __make_signed<char16_t>)
(__make_signed<char32_t>)): Define unconditionally.
* testsuite/20_util/make_signed/requirements/typedefs-3.cc: Check
wchar_t, char16_t and char32_t are transformed correctly.
* testsuite/20_util/make_signed/requirements/typedefs_neg.cc: Adjust
dg-error lineno.
* testsuite/20_util/make_unsigned/requirements/typedefs-3.cc: Check
wchar_t, char16_t and char32_t are transformed correctly.
* testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc: Adjust
dg-error lineno.
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/include/std/type_traits
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs-3.cc
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/make_signed/requirements/typedefs_neg.cc
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs-3.cc
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc
>From gcc-bugs-return-606154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:10:50 2018
Return-Path: <gcc-bugs-return-606154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66211 invoked by alias); 31 May 2018 14:10: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 65565 invoked by uid 55); 31 May 2018 14:10:44 -0000
From: "cesar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85879] [6/7/8/9 Regression] ICE in expand_debug_locations, at cfgexpand.c:5405
Date: Thu, 31 May 2018 14: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cesar 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: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85879-4-tmSEpyYeSt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03049.txt.bz2
Content-length: 1008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85879
--- Comment #4 from cesar at gcc dot gnu.org ---
Author: cesar
Date: Thu May 31 14:10:10 2018
New Revision: 261025
URL: https://gcc.gnu.org/viewcvs?rev=261025&root=gcc&view=rev
Log:
Fix PR middle-end/85879
gcc/
* gimplify.c (gimplify_adjust_omp_clauses): Add 'remove = true'
when emitting error on private/firstprivate reductions.
* omp-low.c (lower_omp_target): Avoid reference-type processing
on pointers for firstprivate clause.
gcc/testsuite/
* gfortran.dg/goacc/pr77371-1.f90: New test.
* gfortran.dg/goacc/pr77371-2.f90: New test.
* gfortran.dg/goacc/pr85879.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/goacc/pr77371-1.f90
trunk/gcc/testsuite/gfortran.dg/goacc/pr77371-2.f90
trunk/gcc/testsuite/gfortran.dg/goacc/pr85879.f90
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimplify.c
trunk/gcc/omp-low.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-606155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:11:21 2018
Return-Path: <gcc-bugs-return-606155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68705 invoked by alias); 31 May 2018 14:11: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 68652 invoked by uid 48); 31 May 2018 14:11:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85951] make_signed and make_unsigned are incorrect for wchar_t, char16_t, and char32_t
Date: Thu, 31 May 2018 14: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: 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-85951-4-1bHvT6xirk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03050.txt.bz2
Content-length: 152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85951
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for trunk and 8.2 so far.
>From gcc-bugs-return-606156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:17:14 2018
Return-Path: <gcc-bugs-return-606156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128772 invoked by alias); 31 May 2018 14:17: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 128650 invoked by uid 48); 31 May 2018 14:17:07 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86004] [9 regression] Several lto test cases begin failing with r260963
Date: Thu, 31 May 2018 14:17: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: 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-86004-4-YdcDKJb3xt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86004-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03051.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86004
--- Comment #2 from seurer at gcc dot gnu.org ---
Sorry about that. The actual complaints are about a missing plugin from the
loader. I've never seen anything like that before.
gcc/testsuite/gfortran/gfortran.log:/usr/bin/ld: /tmp/ccxyE8Zx.lto.o: plugin
needed to handle lto object
seurer@genoa:~/gcc/build/gcc-trunk$ ld --version
GNU ld (GNU Binutils for Ubuntu) 2.26.1
I don't see this problem on a newer system that has binutils version 2.30 on it
so this is probably a problem with binutils.
>From gcc-bugs-return-606157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:51:46 2018
Return-Path: <gcc-bugs-return-606157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78927 invoked by alias); 31 May 2018 14:51: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 76431 invoked by uid 48); 31 May 2018 14:51:42 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86004] [9 regression] Several lto test cases begin failing with r260963
Date: Thu, 31 May 2018 14:51: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: 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-86004-4-PPMZKoXdSC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86004-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03052.txt.bz2
Content-length: 267
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86004
--- Comment #3 from seurer at gcc dot gnu.org ---
I tried a couple of different versions of binutils on one system where this was
occurring and it happens with binutils 2.26 but doesn't with 2.27 (and later).
>From gcc-bugs-return-606158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:52:55 2018
Return-Path: <gcc-bugs-return-606158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83333 invoked by alias); 31 May 2018 14:52: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 83303 invoked by uid 48); 31 May 2018 14:52:51 -0000
From: "gcc-bugs at oxyware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86000] ICE with requires statement in a non constexpr if
Date: Thu, 31 May 2018 14: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: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc-bugs at oxyware 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-86000-4-mA6pgDdZ4p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86000-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86000-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03053.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86000
--- Comment #1 from Hubert Matthews <gcc-bugs at oxyware dot com> ---
template <typename T>
int f()
{
bool check = requires { 3 > 4; };
if (check) return 1;
else return 2;
}
compiles cleanly and gives the expected result. This is essentially the same
code but with the check performed separately and stored in an intermediate
variable.
>From gcc-bugs-return-606159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 14:53:31 2018
Return-Path: <gcc-bugs-return-606159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84184 invoked by alias); 31 May 2018 14: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 84149 invoked by uid 48); 31 May 2018 14:53:27 -0000
From: "gcc-bugs at oxyware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86000] ICE with requires statement in a non constexpr if
Date: Thu, 31 May 2018 14: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc-bugs at oxyware 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-86000-4-9KUebFMwf2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86000-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86000-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03054.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86000
--- Comment #2 from Hubert Matthews <gcc-bugs at oxyware dot com> ---
template <typename T>
int f()
{
bool check = requires { 3 > 4; };
if (check) return 1;
else return 2;
}
compiles cleanly and gives the expected result. This is essentially the same
code but with the check performed separately and stored in an intermediate
variable.
>From gcc-bugs-return-606160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:03:17 2018
Return-Path: <gcc-bugs-return-606160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13957 invoked by alias); 31 May 2018 15:03: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 13849 invoked by uid 55); 31 May 2018 15:03:12 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Thu, 31 May 2018 15: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: 8.1.0
X-Bugzilla-Keywords: missed-optimization
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85829-4-28nLh0nBom@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03055.txt.bz2
Content-length: 3002
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #5 from Sebastian Peryt <sebastian.peryt at intel dot com> ---
I have made measurements on HSW comparing
-mtune-ctrl=movx,partial_reg_dependency -Ofast -march=haswell to -Ofast
-mtune=haswell and I see improvements on EEMBC benchmarks.
automotive
=========
aifftr01 (default) - goodperf: Runtime improvement of 2.6% (time).
aiifft01 (default) - goodperf: Runtime improvement of 2.2% (time).
networking
=========
ip_pktcheckb1m (default) - goodperf: Runtime improvement of 3.8% (time).
ip_pktcheckb2m (default) - goodperf: Runtime improvement of 5.2% (time).
ip_pktcheckb4m (default) - goodperf: Runtime improvement of 4.4% (time).
ip_pktcheckb512k (default) - goodperf: Runtime improvement of 4.2% (time).
telecom
=========
fft00data_1 (default) - goodperf: Runtime improvement of 8.4% (time).
fft00data_2 (default) - goodperf: Runtime improvement of 8.6% (time).
fft00data_3 (default) - goodperf: Runtime improvement of 9.0% (time).
--- Comment #6 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Thu May 31 15:02:36 2018
New Revision: 261026
URL: https://gcc.gnu.org/viewcvs?rev=261026&root=gcc&view=rev
Log:
x86: Re-enable partial_reg_dependency and movx for Haswell
r254152 disabled partial_reg_dependency and movx for Haswell and newer
Intel processors. r258972 restored them for skylake-avx512. For Haswell,
movx improves performance. But partial_reg_stall may be better than
partial_reg_dependency in theory. We will investigate performance impact
of partial_reg_stall vs partial_reg_dependency on Haswell for GCC 9. In
the meantime, this patch restores both partial_reg_dependency and mox for
Haswell in GCC 8.
On Haswell, improvements for EEMBC benchmarks with
-mtune-ctrl=movx,partial_reg_dependency -Ofast -march=haswell
vs
-Ofast -mtune=haswell
are
automotive
=========
aifftr01 (default) - goodperf: Runtime improvement of 2.6% (time).
aiifft01 (default) - goodperf: Runtime improvement of 2.2% (time).
networking
=========
ip_pktcheckb1m (default) - goodperf: Runtime improvement of 3.8% (time).
ip_pktcheckb2m (default) - goodperf: Runtime improvement of 5.2% (time).
ip_pktcheckb4m (default) - goodperf: Runtime improvement of 4.4% (time).
ip_pktcheckb512k (default) - goodperf: Runtime improvement of 4.2% (time).
telecom
=========
fft00data_1 (default) - goodperf: Runtime improvement of 8.4% (time).
fft00data_2 (default) - goodperf: Runtime improvement of 8.6% (time).
fft00data_3 (default) - goodperf: Runtime improvement of 9.0% (time).
PR target/85829
* config/i386/x86-tune.def: Re-enable partial_reg_dependency
and movx for Haswell.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/x86-tune.def
>From gcc-bugs-return-606161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:07:51 2018
Return-Path: <gcc-bugs-return-606161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17536 invoked by alias); 31 May 2018 15: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 17482 invoked by uid 48); 31 May 2018 15:07:47 -0000
From: "foom at fuhm dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
Date: Thu, 31 May 2018 15: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: foom at fuhm 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: cc
Message-ID: <bug-86005-4-UDTcGGuFtL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03056.txt.bz2
Content-length: 1185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
James Y Knight <foom at fuhm dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |foom at fuhm dot net
--- Comment #4 from James Y Knight <foom at fuhm dot net> ---
I think if RISCV wants to use out-of-line lock-free atomic helpers, it should
give those another function name (for example,
__sync_fetch_and_##OP##_##WIDTH), and provide them in libgcc.a, the same as the
other architectures which use such out-of-line helpers.
(But also, why doesn't it implement __atomic_add_fetch inline?)
Since lock-free helper functions can be linked into a process as many times as
you like without correctness issues, it's safe, and preferable, to provide them
in the static runtime lib.
That is quite unlike a potentially-locking __atomic_* function, which must
share the same lock across the whole process, and thus must have only one
implementation in a process, which is why they're provided separately by
libatomic.so.
It's not a good idea to conflate the two different things.
>From gcc-bugs-return-606162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:17:19 2018
Return-Path: <gcc-bugs-return-606162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105322 invoked by alias); 31 May 2018 15:17: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 105235 invoked by uid 55); 31 May 2018 15:17:14 -0000
From: "wilson at tuliptree dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
Date: Thu, 31 May 2018 15: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilson at tuliptree 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-86005-4-16k4kXoPWv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03057.txt.bz2
Content-length: 797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #5 from Jim Wilson <wilson at tuliptree dot org> ---
On Thu, 2018-05-31 at 05:40 +0000, asb at lowrisc dot org wrote:
> Actually I think this bug is wider in scope than I first thought. GCC
> will also
> intermix __atomic libcalls and inline instruction sequences with
> -march=rv32ia
> when values less than XLEN in size are accessed.
FYI I have a prototype patch to fix this. I copied the subword atomic
support from the ppc port, and hacked it to work. I haven't done the
fences yet, so it probably won't work if you have more than one thread,
but it works well enough to handle the gcc/g++ testsuites. It also
needs some cleanup to remove more ppc specific stuff. I don't know
when I will have time to finish it though.
>From gcc-bugs-return-606163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:36:50 2018
Return-Path: <gcc-bugs-return-606163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128867 invoked by alias); 31 May 2018 15: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 122881 invoked by uid 48); 31 May 2018 15:36:45 -0000
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
Date: Thu, 31 May 2018 15: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: wilson 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-86005-4-j0FojO3TaB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03058.txt.bz2
Content-length: 399
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
Jim Wilson <wilson at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-31
Ever confirmed|0 |1
>From gcc-bugs-return-606165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:38:44 2018
Return-Path: <gcc-bugs-return-606165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7915 invoked by alias); 31 May 2018 15: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 7864 invoked by uid 48); 31 May 2018 15:38:39 -0000
From: "joshua.r.marshall.1991 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86015] New: Better handling of iterator distances
Date: Thu, 31 May 2018 15: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.r.marshall.1991 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-86015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03060.txt.bz2
Content-length: 1261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
Bug ID: 86015
Summary: Better handling of iterator distances
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: joshua.r.marshall.1991 at gmail dot com
Target Milestone: ---
I'm writing containers for containers to track usage and operations for
performance metrics. I've found it impossible to allow implicit conversion
from integer types to a distance object without introducing conflicting
resolutions for all basic math operations. It occasionally leads to errors
like the following:
/usr/bin/../lib/gcc/x86_64-linux-gnu/7.3.0/../../../../include/c++/7.3.0/bits/stl_algo.h:2495:17:
error: no viable conversion from 'int' to
'distance_counter<__gnu_cxx::__normal_iterator<long *, std::vector<long,
std::allocator<long> > >, long>'
_Distance __len22 = 0;
In this instance, I think the best way to handle this is to change
stl_algo.h:2495: _Distance __len22 = 0;
to
stl_algo.h:2495: _Distance __len22 = _Distance(0);
Am I just doing something dumb, or is this reasonable?
>From gcc-bugs-return-606164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:38:00 2018
Return-Path: <gcc-bugs-return-606164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6879 invoked by alias); 31 May 2018 15:38: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 6771 invoked by uid 55); 31 May 2018 15:37:54 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Thu, 31 May 2018 15:38: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: missed-optimization
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85829-4-jRvug0wFz7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03059.txt.bz2
Content-length: 1922
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #7 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Thu May 31 15:37:22 2018
New Revision: 261028
URL: https://gcc.gnu.org/viewcvs?rev=261028&root=gcc&view=rev
Log:
x86: Re-enable partial_reg_dependency and movx for Haswell
r254152 disabled partial_reg_dependency and movx for Haswell and newer
Intel processors. r258972 restored them for skylake-avx512. For Haswell,
movx improves performance. But partial_reg_stall may be better than
partial_reg_dependency in theory. We will investigate performance impact
of partial_reg_stall vs partial_reg_dependency on Haswell for GCC 9. In
the meantime, this patch restores both partial_reg_dependency and mox for
Haswell in GCC 8.
On Haswell, improvements for EEMBC benchmarks with
-mtune-ctrl=movx,partial_reg_dependency -Ofast -march=haswell
vs
-Ofast -mtune=haswell
are
automotive
=========
aifftr01 (default) - goodperf: Runtime improvement of 2.6% (time).
aiifft01 (default) - goodperf: Runtime improvement of 2.2% (time).
networking
=========
ip_pktcheckb1m (default) - goodperf: Runtime improvement of 3.8% (time).
ip_pktcheckb2m (default) - goodperf: Runtime improvement of 5.2% (time).
ip_pktcheckb4m (default) - goodperf: Runtime improvement of 4.4% (time).
ip_pktcheckb512k (default) - goodperf: Runtime improvement of 4.2% (time).
telecom
=========
fft00data_1 (default) - goodperf: Runtime improvement of 8.4% (time).
fft00data_2 (default) - goodperf: Runtime improvement of 8.6% (time).
fft00data_3 (default) - goodperf: Runtime improvement of 9.0% (time).
PR target/85829
* config/i386/x86-tune.def: Re-enable partial_reg_dependency
and movx for Haswell.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/x86-tune.def
>From gcc-bugs-return-606166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:39:58 2018
Return-Path: <gcc-bugs-return-606166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16560 invoked by alias); 31 May 2018 15:39: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 16446 invoked by uid 48); 31 May 2018 15:39:53 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Thu, 31 May 2018 15: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: missed-optimization
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85829-4-ST2E3EAFoR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03061.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 9 and GCC 8.2.
>From gcc-bugs-return-606167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:45:40 2018
Return-Path: <gcc-bugs-return-606167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121452 invoked by alias); 31 May 2018 15:45: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 119463 invoked by uid 48); 31 May 2018 15:45:09 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85993] config/sh/sh.c:10878: suspicious if .. else chain
Date: Thu, 31 May 2018 15: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo 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-85993-4-feFoQVKUSw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85993-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03062.txt.bz2
Content-length: 1708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85993
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-31
Ever confirmed|0 |1
--- Comment #3 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to David Binderman from comment #0)
> config/sh/sh.c:10878:12: warning: duplicated ‘if’ condition
> [-Wduplicated-cond]
>
> Source code is
>
> else if (scratch0 != scratch1)
> {
> emit_move_insn (scratch1, GEN_INT (vcall_offset));
> emit_insn (gen_add2_insn (scratch0, scratch1));
> offset_addr = scratch0;
> }
>
> but earlier is code
>
> else if (scratch0 != scratch1)
> {
> /* scratch0 != scratch1, and we have indexed loads. Get better
> schedule by loading the offset into r1 and using an indexed
> load - then the load of r1 can issue before the load from
> (this_rtx + delta) finishes. */
> emit_move_insn (scratch1, GEN_INT (vcall_offset));
> offset_addr = gen_rtx_PLUS (Pmode, scratch0, scratch1);
> }
>
> Interestingly, the two blocks of code in the ifs aren't the same.
The line 10864 used to be:
else if (! TARGET_SH5 && scratch0 != scratch1)
and I chopped it off to be
else if (scratch0 != scratch1)
when removing support for SH5. I haven't noticed that the 2nd else if block
became unreachable. It can be removed.
>From gcc-bugs-return-606168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:49:56 2018
Return-Path: <gcc-bugs-return-606168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127787 invoked by alias); 31 May 2018 15: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 127703 invoked by uid 48); 31 May 2018 15:49:50 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/68791] Segfault during link/compilation after update.
Date: Thu, 31 May 2018 15: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: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail 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: cc
Message-ID: <bug-68791-4-gE20TUNEuA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03063.txt.bz2
Content-length: 1092
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68791
David Binderman <dcb314 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dcb314 at hotmail dot com
--- Comment #5 from David Binderman <dcb314 at hotmail dot com> ---
For this command line:
~/gcc/results.260789.ubsan/bin/gcc -flto acct.o
I get this:
$ source /tmp/11
../../trunk/gcc/lto-streamer.h:1210:1: runtime error: member access within null
pointer of type 'struct lto_in_decl_state'
lto1: internal compiler error: Segmentation fault
0x25937cf crash_signal
../../trunk/gcc/toplev.c:325
0x1cf8601 lto_file_decl_data_get_var_decl
../../trunk/gcc/lto-streamer.h:1210
0x1cf8601 lto_input_tree_ref(lto_input_block*, data_in*, function*, LTO_tags)
../../trunk/gcc/lto-streamer-in.c:364
0x1cf916d lto_input_tree_1(lto_input_block*, data_in*, LTO_tags, unsigned int)
../../trunk/gcc/lto-streamer-in.c:1489
Object file acct.o attached.
>From gcc-bugs-return-606169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:51:37 2018
Return-Path: <gcc-bugs-return-606169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29859 invoked by alias); 31 May 2018 15: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 26929 invoked by uid 48); 31 May 2018 15:51:32 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/68791] Segfault during link/compilation after update.
Date: Thu, 31 May 2018 15:51: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: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail 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: attachments.created
Message-ID: <bug-68791-4-RFRa6BzZYc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03064.txt.bz2
Content-length: 243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68791
--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
Created attachment 44219
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44219&action=edit
x86_64 object module
>From gcc-bugs-return-606170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 15:55:28 2018
Return-Path: <gcc-bugs-return-606170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14591 invoked by alias); 31 May 2018 15:55: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 14549 invoked by uid 48); 31 May 2018 15:55:24 -0000
From: "joshua.r.marshall.1991 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86015] Better handling of iterator distances
Date: Thu, 31 May 2018 15: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.r.marshall.1991 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-86015-4-uYjBM2p0ex@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03065.txt.bz2
Content-length: 348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
--- Comment #1 from Josh Marshall <joshua.r.marshall.1991 at gmail dot com> ---
It looks like wrappings would be applicable at the following lines:
296, 297, 2438, 2439, 2494, 2495
using
https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/bits/stl_algo.h
as reference.
>From gcc-bugs-return-606171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 16:17:24 2018
Return-Path: <gcc-bugs-return-606171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85794 invoked by alias); 31 May 2018 16:17: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 85725 invoked by uid 48); 31 May 2018 16:17:19 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/68791] Segfault during link/compilation after update.
Date: Thu, 31 May 2018 16:17: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: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail 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-68791-4-Kp2lg1x2Cb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03066.txt.bz2
Content-length: 193
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68791
--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
This bug seems to have been present since some revision before 260047.
>From gcc-bugs-return-606172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 16:29:12 2018
Return-Path: <gcc-bugs-return-606172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121788 invoked by alias); 31 May 2018 16: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 121729 invoked by uid 48); 31 May 2018 16:29:06 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86016] New: New tests for r260978 report excess errors
Date: Thu, 31 May 2018 16:29: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-86016-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03067.txt.bz2
Content-length: 2493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86016
Bug ID: 86016
Summary: New tests for r260978 report excess errors
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: ---
Some of the new tests are reporting excess errors like this:
# of expected passes 14
# of unexpected failures 7
FAIL: gcc.dg/noncompile/pr55976-1.c -O0 (test for excess errors)
FAIL: gcc.dg/noncompile/pr55976-1.c -O1 (test for excess errors)
FAIL: gcc.dg/noncompile/pr55976-1.c -O2 (test for excess errors)
FAIL: gcc.dg/noncompile/pr55976-1.c -O3 -g (test for excess errors)
FAIL: gcc.dg/noncompile/pr55976-1.c -Os (test for excess errors)
FAIL: gcc.dg/noncompile/pr55976-1.c -O2 -flto -fno-use-linker-plugin
-flto-partition=none (test for excess errors)
FAIL: gcc.dg/noncompile/pr55976-1.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (test for excess errors)
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/noncompile/pr55976-1.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O0 -Werror=return-type
-S -o pr55976-1.s
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/noncompile/pr55976-1.c: In
function 't':
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/noncompile/pr55976-1.c:7:20:
error: 'return' with a value, in function returning void [-Werror=return-type]
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/noncompile/pr55976-1.c:7:6:
note: declared here
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/noncompile/pr55976-1.c: In
function 'b':
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/noncompile/pr55976-1.c:8:12:
error: 'return' with no value, in function returning non-void
[-Werror=return-type]
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/noncompile/pr55976-1.c:8:5:
note: declared here
cc1: some warnings being treated as errors
compiler exited with status 1
PASS: gcc.dg/noncompile/pr55976-1.c -O0 function returning void (test for
errors, line 7)
PASS: gcc.dg/noncompile/pr55976-1.c -O0 function returning non-void (test
for errors, line 8)
FAIL: gcc.dg/noncompile/pr55976-1.c -O0 (test for excess errors)
Excess errors:
cc1: some warnings being treated as errors
>From gcc-bugs-return-606173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 17:05:22 2018
Return-Path: <gcc-bugs-return-606173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23697 invoked by alias); 31 May 2018 17: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 23617 invoked by uid 55); 31 May 2018 17:05:16 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82063] issues with arguments enabled by -Wall
Date: Thu, 31 May 2018 17:05: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: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82063-4-CrhZ9zv2IP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82063-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82063-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03068.txt.bz2
Content-length: 2973
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82063
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Thu May 31 17:04:43 2018
New Revision: 261030
URL: https://gcc.gnu.org/viewcvs?rev=261030&root=gcc&view=rev
Log:
PR c/82063 - issues with arguments enabled by -Wall
gcc/c-family/ChangeLog:
PR c/82063
* c.opt (-Wno-alloc-size-larger-than): New option.
* doc/invoke.texi (-Walloc-size-larger-than): Update.
gcc/ChangeLog:
PR c/82063
* calls.c (alloc_max_size): Correct a logic error/typo.
Treat excessive arguments as infinite. Warn for invalid arguments.
gcc/testsuite/ChangeLog:
PR c/82063
* gcc.dg/Walloc-size-larger-than-1.c: New test.
* gcc.dg/Walloc-size-larger-than-10.c: New test.
* gcc.dg/Walloc-size-larger-than-11.c: New test.
* gcc.dg/Walloc-size-larger-than-12.c: New test.
* gcc.dg/Walloc-size-larger-than-13.c: New test.
* gcc.dg/Walloc-size-larger-than-14.c: New test.
* gcc.dg/Walloc-size-larger-than-15.c: New test.
* gcc.dg/Walloc-size-larger-than-16.c: New test.
* gcc.dg/Walloc-size-larger-than-17.c: New test.
* gcc.dg/Walloc-size-larger-than-2.c: New test.
* gcc.dg/Walloc-size-larger-than-3.c: New test.
* gcc.dg/Walloc-size-larger-than-4.c: New test.
* gcc.dg/Walloc-size-larger-than-5.c: New test.
* gcc.dg/Walloc-size-larger-than-6.c: New test.
* gcc.dg/Walloc-size-larger-than-7.c: New test.
* gcc.dg/Walloc-size-larger-than-8.c: New test.
* gcc.dg/Walloc-size-larger-than-9.c: New test.
* gcc.dg/Walloc-size-larger-than.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-1.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-10.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-11.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-12.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-13.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-14.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-15.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-16.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-17.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-2.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-3.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-4.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-5.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-6.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-7.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-8.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than-9.c
trunk/gcc/testsuite/gcc.dg/Walloc-size-larger-than.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c.opt
trunk/gcc/calls.c
trunk/gcc/doc/invoke.texi
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-606174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 17:16:52 2018
Return-Path: <gcc-bugs-return-606174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61100 invoked by alias); 31 May 2018 17:16: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 60697 invoked by uid 48); 31 May 2018 17:16:45 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86017] New: multiple consecutive calls to bzero/memset not merged
Date: Thu, 31 May 2018 17: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: 8.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-86017-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03069.txt.bz2
Content-length: 3029
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86017
Bug ID: 86017
Summary: multiple consecutive calls to bzero/memset not merged
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Even though the two functions defined in the test case below are equivalent,
GCC emits considerably less efficient code the one with multiple calls to
memset than for the one with just a single call. Clang emits the same
optimally efficient code for both.
$ cat b.c && gcc -O2 -S -Wall -Wextra -fdump-tree-optimized=/dev/stdout
-o/dev/stdout b.c
void f (void*);
void g (void)
{
char a[8];
__builtin_memset (a, 0, 8);
f (a);
}
void h (void)
{
char a[8];
__builtin_memset (a, 0, 1);
__builtin_memset (a + 1, 0, 1);
__builtin_memset (a + 2, 0, 1);
__builtin_memset (a + 3, 0, 1);
__builtin_memset (a + 4, 0, 1);
__builtin_memset (a + 5, 0, 1);
__builtin_memset (a + 6, 0, 1);
__builtin_memset (a + 7, 0, 1);
f (a);
}
.file "b.c"
.text
;; Function g (g, funcdef_no=0, decl_uid=1958, cgraph_uid=0, symbol_order=0)
g ()
{
char a[8];
<bb 2> [local count: 1073741825]:
__builtin_memset (&a, 0, 8);
f (&a);
a ={v} {CLOBBER};
return;
}
.p2align 4,,15
.globl g
.type g, @function
g:
.LFB0:
.cfi_startproc
subq $24, %rsp
.cfi_def_cfa_offset 32
movq $0, 8(%rsp)
leaq 8(%rsp), %rdi
call f
addq $24, %rsp
.cfi_def_cfa_offset 8
ret
.cfi_endproc
.LFE0:
.size g, .-g
;; Function h (h, funcdef_no=1, decl_uid=1962, cgraph_uid=1, symbol_order=1)
h ()
{
char a[8];
<bb 2> [local count: 1073741825]:
MEM[(void *)&a] = 0;
__builtin_memset (&MEM[(void *)&a + 1B], 0, 1);
__builtin_memset (&MEM[(void *)&a + 2B], 0, 1);
__builtin_memset (&MEM[(void *)&a + 3B], 0, 1);
__builtin_memset (&MEM[(void *)&a + 4B], 0, 1);
__builtin_memset (&MEM[(void *)&a + 5B], 0, 1);
__builtin_memset (&MEM[(void *)&a + 6B], 0, 1);
__builtin_memset (&MEM[(void *)&a + 7B], 0, 1);
f (&a);
a ={v} {CLOBBER};
return;
}
.p2align 4,,15
.globl h
.type h, @function
h:
.LFB1:
.cfi_startproc
subq $24, %rsp
.cfi_def_cfa_offset 32
leaq 8(%rsp), %rdi
movb $0, 8(%rsp)
movb $0, 9(%rsp)
movb $0, 10(%rsp)
movb $0, 11(%rsp)
movb $0, 12(%rsp)
movb $0, 13(%rsp)
movb $0, 14(%rsp)
movb $0, 15(%rsp)
call f
addq $24, %rsp
.cfi_def_cfa_offset 8
ret
.cfi_endproc
.LFE1:
.size h, .-h
.ident "GCC: (GNU) 8.1.1 20180522"
.section .note.GNU-stack,"",@progbits
>From gcc-bugs-return-606175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 17:18:33 2018
Return-Path: <gcc-bugs-return-606175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91541 invoked by alias); 31 May 2018 17:18: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 85248 invoked by uid 48); 31 May 2018 17:18:27 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86017] multiple consecutive calls to bzero/memset not merged
Date: Thu, 31 May 2018 17: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.0
X-Bugzilla-Keywords: missed-optimization
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-86017-4-WsQzpGBJ36@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86017-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03070.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86017
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=86010
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also bug 86010 for a related missed optimization (that one is a regression
while this bug does not appear to be).
>From gcc-bugs-return-606176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 17:22:42 2018
Return-Path: <gcc-bugs-return-606176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6662 invoked by alias); 31 May 2018 17:22: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 6564 invoked by uid 48); 31 May 2018 17:22:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85931] -Wsizeof-pointer-memaccess for strncpy with size of source
Date: Thu, 31 May 2018 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: 8.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-85931-4-ACxOLNONEa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85931-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03071.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85931
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01698.html
>From gcc-bugs-return-606177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 17:27:40 2018
Return-Path: <gcc-bugs-return-606177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119945 invoked by alias); 31 May 2018 17:27: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 119918 invoked by uid 48); 31 May 2018 17:27:35 -0000
From: "joshua.r.marshall.1991 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86015] Better handling of iterator distances
Date: Thu, 31 May 2018 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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.r.marshall.1991 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-86015-4-NyGyjfXefR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03072.txt.bz2
Content-length: 229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
--- Comment #2 from Josh Marshall <joshua.r.marshall.1991 at gmail dot com> ---
There are also lines close by which call std::distance() which need to be
similarly wrapped.
>From gcc-bugs-return-606178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 17:56:51 2018
Return-Path: <gcc-bugs-return-606178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18208 invoked by alias); 31 May 2018 17:56: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 18069 invoked by uid 48); 31 May 2018 17:56:46 -0000
From: "rconde01 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86018] New: Incorrect unused warning for int passed by reference to lambda
Date: Thu, 31 May 2018 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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rconde01 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-86018-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03073.txt.bz2
Content-length: 1625
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86018
Bug ID: 86018
Summary: Incorrect unused warning for int passed by reference
to lambda
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rconde01 at hotmail dot com
Target Milestone: ---
https://godbolt.org/g/XLjyWM
When compiled with: -std=c++14 -Wall -Wextra
#include <string>
typedef void(*TheFP)(int & e);
class MyObject
{
public:
void DoSomething(TheFP)
{
}
};
void myFunc()
{
MyObject m;
m.DoSomething
(
[](auto i)
{
i = 5;
}
);
}
----------------------------------------------------------------------------
gives:
In instantiation of 'myFunc()::<lambda(auto:1)> [with auto:1 = int]':
19:18: required by substitution of 'template<class auto:1>
myFunc()::<lambda(auto:1)>::operator decltype (((const
myFunc()::<lambda(auto:1)>*)((const myFunc()::<lambda(auto:1)>*
const)0))->operator()(static_cast<auto:1&&>(<anonymous>))) (*)(auto:1)() const
[with auto:1 = int&]'
23:5: required from here
19:17: warning: parameter 'i' set but not used [-Wunused-but-set-parameter]
[](auto i)
~~~~~^
----------------------------------------------------------------------------
The workaround is to change it to:
void myFunc()
{
MyObject m;
m.DoSomething
(
[](auto & i)
{
i = 5;
}
);
}
>From gcc-bugs-return-606179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 18:25:49 2018
Return-Path: <gcc-bugs-return-606179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85108 invoked by alias); 31 May 2018 18: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 85071 invoked by uid 48); 31 May 2018 18:25:44 -0000
From: "klempner at imsanet dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86019] New: Unref implementation using atomic_thread_fence generates worse code on x86-64 in gcc 8.1 than 7.3
Date: Thu, 31 May 2018 18: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: klempner at imsanet 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
Message-ID: <bug-86019-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03074.txt.bz2
Content-length: 1734
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86019
Bug ID: 86019
Summary: Unref implementation using atomic_thread_fence
generates worse code on x86-64 in gcc 8.1 than 7.3
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: klempner at imsanet dot org
Target Milestone: ---
See https://godbolt.org/g/Tu80RI (specifically the godegen for do_unref3())
Simplified version: https://godbolt.org/g/Xbn6n6
This is the unref half of a refcount implementation:
#include <atomic>
std::atomic<int> refcount;
bool do_unref() {
int old_count = refcount.fetch_sub(1, std::memory_order_release);
if (old_count == 1) {
std::atomic_thread_fence(std::memory_order_acquire);
}
return old_count == 1;
}
In particular, unref needs release semantics on every decrement, but only needs
acquire semantics on the last decrement.
std::atomic_thread_fence(std::memory_order_acquire) should be (approximately) a
no-op on x86.
gcc 7.3 generated the right code here:
do_unref():
lock sub DWORD PTR refcount[rip], 1
sete al
ret
gcc 8.1 generates a branch choosing between duplicate codepaths based on
whether old_count == 1:
do_unref():
mov eax, -1
lock xadd DWORD PTR refcount[rip], eax
cmp eax, 1
je .L4
cmp eax, 1
sete al
ret
.L4:
cmp eax, 1
sete al
ret
It also appears to fail to optimize based on decrementing the constant value 1.
>From gcc-bugs-return-606180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 18:30:00 2018
Return-Path: <gcc-bugs-return-606180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35275 invoked by alias); 31 May 2018 18:30: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 27769 invoked by uid 48); 31 May 2018 18:29:52 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86019] Unref implementation using atomic_thread_fence generates worse code on x86-64 in gcc 8.1 than 7.3
Date: Thu, 31 May 2018 18:30: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: 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: cf_gcctarget bug_file_loc component
Message-ID: <bug-86019-4-hu0pRJidya@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86019-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86019-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03075.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86019
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64
URL| |missed-optimization
Component|c++ |target
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I suspect memory_order_acquire is being treated as a compiler memory barrier
and that is causing an empty basic block (it is not truly empty).
>From gcc-bugs-return-606181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:14:50 2018
Return-Path: <gcc-bugs-return-606181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122068 invoked by alias); 31 May 2018 19: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 116647 invoked by uid 48); 31 May 2018 19:14:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86015] Better handling of iterator distances
Date: Thu, 31 May 2018 19: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: 7.3.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 component everconfirmed bug_severity
Message-ID: <bug-86015-4-f1MAfqZYWs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03076.txt.bz2
Content-length: 866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-31
Component|c++ |libstdc++
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think all those _Distance types comes from
iterator_traits<Iter>::difference_type, and by my reading of the standard an
iterator's difference type is required to be a signed integer type.
But it seems harmless to make the suggested change, it won't affect any valid
code.
>From gcc-bugs-return-606182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:21:10 2018
Return-Path: <gcc-bugs-return-606182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25124 invoked by alias); 31 May 2018 19:21: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 21753 invoked by uid 55); 31 May 2018 19:21:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78870] Support std::filesystem on Windows
Date: Thu, 31 May 2018 19:21: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: patch
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78870-4-IL19AX4gzv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03077.txt.bz2
Content-length: 14343
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 31 19:20:24 2018
New Revision: 261034
URL: https://gcc.gnu.org/viewcvs?rev=261034&root=gcc&view=rev
Log:
PR libstdc++/78870 support std::filesystem on Windows
PR libstdc++/78870 support std::filesystem on Windows
* config.h.in: Regenerate.
* configure: Regenerate.
* configure.ac: Check for link, readlink and symlink.
* include/bits/fs_path.h (path::operator/=(const path&)): Move
definition out of class body.
(path::is_absolute(), path::_M_append(path)): Likewise.
(operator<<(basic_ostream, const path&)): Use std::quoted directly.
(operator>>(basic_istream, path&)): Likewise.
(u8path): Reorder definitions and fix Windows implementation.
(path::is_absolute()): Define inline and fix for Windows.
[!_GLIBCXX_FILESYSTEM_IS_WINDOWS] (path::operator/=(const path&)):
Define POSIX version inline.
(path::_M_append(path)): Define inline.
* include/experimental/bits/fs_path.h (path::is_absolute()): Move
definition out of class body.
(operator<<(basic_ostream, const path&)): Fix type of delimiter and
escape characters.
(operator>>(basic_istream, path&)): Likewise.
(path::is_absolute()): Define inline and fix for Windows.
* src/filesystem/dir-common.h (__gnu_posix): New namespace.
(__gnu_posix::char_type, __gnu_posix::DIR, __gnu_posix::dirent)
(__gnu_posix::opendir, __gnu_posix::readdir, __gnu_posix::closedir):
Define as adaptors for Windows functions/types or as
using-declarations for POSIX functions/types.
(_Dir_base, get_file_type): Qualify names to use declarations from
__gnu_posix namespace.
(_Dir_base::is_dor_or_dotdot): New helper functions.
* src/filesystem/dir.cc (_Dir, recursive_directory_iterator): Qualify
names to use declarations from __gnu_posix namespace.
* src/filesystem/ops-common.h (__gnu_posix): New nested namespace.
(__gnu_posix::open, __gnu_posix::close, __gnu_posix::stat_type)
(__gnu_posix::stat, __gnu_posix::lstat, __gnu_posix::mode_t)
(__gnu_posix::chmod, __gnu_posix::mkdir, __gnu_posix::getcwd)
(__gnu_posix::chdir, __gnu_posix::utimbuf, __gnu_posix::utime)
(__gnu_posix::rename, __gnu_posix::truncate, __gnu_posix::char_type):
Define as adaptors for Windows functions/types or as
using-declarations for POSIX functions/types.
(stat_type, do_copy_file): Qualify names to use declarations from
__gnu_posix namespace.
(do_space): Declare new function.
(make_file_type): Only use S_ISLNK if defined.
* src/filesystem/ops.cc (char_ptr, filesystem::canonical): Use
path::value_type not char.
(filesystem::copy, create_dir, filesystem::create_directory): Qualify
names to use declarations from __gnu_posix namespace.
(filesystem::create_hard_link): Check HAVE_LINK autoconf macro and
add implementation for Windows.
(filesystem::create_symlink): Check HAVE_SYMLINK autoconf macro.
(filesystem::current_path(error_code&)): Use __gnu_posix::getcwd.
[!_PC_PATH_MAX]: Don't use pathconf.
[PATH_MAX]: Use if defined.
(filesystem::current_path(const path&, error_code&))
(filesystem::equivalent, do_stat, filesystem::hard_link_count)
(filesystem::last_write_time, filesystem::permissions): Use names
from __gnu_posix.
(filesystem::read_symlink): Check HAVE_READLINK autoconf macro.
(filesystem::remove) [_GLIBCXX_FILESYSTEM_IS_WINDOWS]: Add
implementation for Windows.
(filesystem::rename, filesystem::resize_file): Use names from
__gnu_posix.
(filesystem::space): Use do_space.
[_GLIBCXX_FILESYSTEM_IS_WINDOWS]: Get absolute path to directory.
(filesystem::status, filesystem::symlink_status): Use names from
__gnu_posix.
(filesystem::temp_directory_path): Add implementation for Windows.
* src/filesystem/path.cc (dot): Define constant.
(path::replace_extension): Use dot.
(path::_M_find_extension): Likewise. Use path::string_type not
std::string.
(path::_M_split_cmpts): Use dot.
(filesystem_error::_M_get_what): Use u8string() not native().
* src/filesystem/std-dir.cc (_Dir, recursive_directory_iterator):
Qualify names to use declarations from __gnu_posix namespace.
* src/filesystem/std-ops.cc (filesystem::absolute(const path&)): Use
correct error_code.
(filesystem::absolute(const path&, error_code&)): Add implementation
for Windows.
(char_ptr, filesystem::canonical): Use path::value_type not char.
(do_copy_file): Use names from __gnu_posix.
[_GLIBCXX_FILESYSTEM_IS_WINDOWS]: Do not use fchmod, fchmodat or
sendfile.
(filesystem::copy, create_dir, filesystem::create_directory): Qualify
names to use declarations from __gnu_posix namespace.
(filesystem::create_hard_link): Check HAVE_LINK autoconf macro and
add implementation for Windows.
(filesystem::create_symlink): Check HAVE_SYMLINK autoconf macro.
(filesystem::current_path(error_code&)): Use __gnu_posix::getcwd.
[!_PC_PATH_MAX]: Don't use pathconf.
[PATH_MAX]: Use if defined.
(filesystem::current_path(const path&, error_code&))
(filesystem::equivalent, do_stat, filesystem::hard_link_count)
(filesystem::last_write_time, filesystem::permissions): Use names
from __gnu_posix.
(filesystem::read_symlink): Check HAVE_READLINK autoconf macro.
(filesystem::remove) [_GLIBCXX_FILESYSTEM_IS_WINDOWS]: Add
implementation for Windows.
(filesystem::rename, filesystem::resize_file): Use names from
__gnu_posix.
(do_space): Define.
(filesystem::space): Use do_space.
(filesystem::status, filesystem::symlink_status): Use names from
__gnu_posix.
(filesystem::temp_directory_path): Add implementation for Windows.
* src/filesystem/std-path.cc
[_GLIBCXX_FILESYSTEM_IS_WINDOWS] (path::operator/=(const path&)):
Define for Windows.
(dot): Define constant.
(path::replace_extension, is_dot): Use dot.
(path::lexically_normal): Check _M_type instead of calling
non-existent function.
(path::_M_find_extension): Use dot. Use path::string_type not
std::string.
(path::_M_split_cmpts): Use dot.
(filesystem_error::_M_get_what): Use u8string() not native().
* testsuite/27_io/filesystem/iterators/directory_iterator.cc: Do not
use symlinks.
* testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc:
Likewise.
* testsuite/27_io/filesystem/operations/absolute.cc: Use
__gnu_test::root_path() instead of "/" and add Windows-specific tests.
* testsuite/27_io/filesystem/operations/canonical.cc: Use
path::string() to get narrow string, not path::native().
* testsuite/27_io/filesystem/operations/copy.cc: Construct fstreams
with std::filesystem::path not std::basic_string.
* testsuite/27_io/filesystem/operations/copy_file.cc: Likewise.
* testsuite/27_io/filesystem/operations/exists.cc: Use
__gnu_test::root_path() instead of "/".
* testsuite/27_io/filesystem/operations/is_empty.cc: Construct
fstreams with std::filesystem::path not std::basic_string.
* testsuite/27_io/filesystem/operations/last_write_time.cc: Use
path::string() to get narrow string.
* testsuite/27_io/filesystem/operations/space.cc: Check results for
errors, expect sensible values otherwise.
* testsuite/27_io/filesystem/operations/temp_directory_path.cc: Add
helpers for adjusting the environment on Windows.
* testsuite/27_io/filesystem/path/append/path.cc: Test
Windows-specific behaviour.
* testsuite/27_io/filesystem/path/construct/format.cc: Fix creation
of path::string_type objects.
* testsuite/27_io/filesystem/path/construct/locale.cc: Compare native
string to wide string on Windows.
* testsuite/27_io/filesystem/path/decompose/root_directory.cc: Allow
for backslash as root-directory.
* testsuite/27_io/filesystem/path/decompose/stem.cc: Use
path::string() to get narrow string.
* testsuite/27_io/filesystem/path/itr/traversal.cc: Test Windows-style
paths.
* testsuite/27_io/filesystem/path/native/string.cc: Use string_type
not std::string.
* testsuite/27_io/filesystem/path/query/is_absolute.cc: Adjust for
different definintion of absolute paths on Windows.
* testsuite/experimental/filesystem/iterators/directory_iterator.cc:
Do not use symlinks.
* testsuite/experimental/filesystem/operations/absolute.cc: Test
Windows behaviour.
* testsuite/experimental/filesystem/operations/copy.cc: Construct
fstreams with NTCTS not std::basic_string.
* testsuite/experimental/filesystem/operations/copy_file.cc: Likewise.
* testsuite/experimental/filesystem/operations/exists.cc: Use
__gnu_test::root_path() instead of "/".
* testsuite/experimental/filesystem/operations/is_empty.cc: Construct
fstreams with NTCTS not std::basic_string.
* testsuite/experimental/filesystem/operations/last_write_time.cc:
Use path::string() to get narrow string.
* testsuite/experimental/filesystem/operations/space.cc: Use
__gnu_test::root_path() instead of "/".
* testsuite/experimental/filesystem/operations/temp_directory_path.cc:
Add helpers for adjusting the environment on Windows.
* testsuite/experimental/filesystem/path/append/path.cc: Use
path::string() to get narrow strings for comparisons.
* testsuite/experimental/filesystem/path/concat/path.cc: Likewise.
* testsuite/experimental/filesystem/path/decompose/root_directory.cc:
Likewise.
* testsuite/experimental/filesystem/path/decompose/stem.cc: Likewise.
* testsuite/experimental/filesystem/path/native/string.cc: Use
string_type not std::string.
* testsuite/experimental/filesystem/path/query/is_absolute.cc:
Adjust for different definintion of absolute paths on Windows.
* testsuite/util/testsuite_fs.h (__gnu_test::root_path()): New
function.
(__gnu_test::scoped_file): Construct fstreams with NTCTS not
std::basic_string.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/config.h.in
trunk/libstdc++-v3/configure
trunk/libstdc++-v3/configure.ac
trunk/libstdc++-v3/include/bits/fs_path.h
trunk/libstdc++-v3/include/experimental/bits/fs_path.h
trunk/libstdc++-v3/src/filesystem/dir-common.h
trunk/libstdc++-v3/src/filesystem/dir.cc
trunk/libstdc++-v3/src/filesystem/ops-common.h
trunk/libstdc++-v3/src/filesystem/ops.cc
trunk/libstdc++-v3/src/filesystem/path.cc
trunk/libstdc++-v3/src/filesystem/std-dir.cc
trunk/libstdc++-v3/src/filesystem/std-ops.cc
trunk/libstdc++-v3/src/filesystem/std-path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/iterators/directory_iterator.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/absolute.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/canonical.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/copy.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/copy_file.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/exists.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/is_empty.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/last_write_time.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/space.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/temp_directory_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/append/path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/format.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/locale.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/root_directory.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/stem.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/itr/traversal.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/native/string.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/is_absolute.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/iterators/directory_iterator.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/absolute.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/copy.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/copy_file.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/exists.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/is_empty.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/last_write_time.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/space.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/operations/temp_directory_path.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/append/path.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/concat/path.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/decompose/root_directory.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/decompose/stem.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/native/string.cc
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/query/is_absolute.cc
trunk/libstdc++-v3/testsuite/util/testsuite_fs.h
>From gcc-bugs-return-606183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:36:57 2018
Return-Path: <gcc-bugs-return-606183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122911 invoked by alias); 31 May 2018 19:36: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 122839 invoked by uid 48); 31 May 2018 19:36:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85670] `std::filesystem` does not compile on mingw-w64
Date: Thu, 31 May 2018 19: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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-85670-4-9hUwZKHNsb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03078.txt.bz2
Content-length: 154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85670
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk now. See PR 78870.
>From gcc-bugs-return-606184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:38:53 2018
Return-Path: <gcc-bugs-return-606184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125108 invoked by alias); 31 May 2018 19:38: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 124989 invoked by uid 48); 31 May 2018 19:38:46 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78870] Support std::filesystem on Windows
Date: Thu, 31 May 2018 19:38: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: patch
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-78870-4-MZLVhG207Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03079.txt.bz2
Content-length: 751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The Filesystem library now builds and mostly works on MinGW (for both the TS
and C++17 versions).
The library is not enabled by default for mingw targets, so you need to build
GCC with --enable-libstdcxx-filesystem-ts
If people can test and confirm it works fine for both mingw and mingw-w64 then
we can enable it by default.
>From gcc-bugs-return-606185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:39:44 2018
Return-Path: <gcc-bugs-return-606185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126300 invoked by alias); 31 May 2018 19:39: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 126195 invoked by uid 48); 31 May 2018 19:39:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78870] Support std::filesystem on Windows
Date: Thu, 31 May 2018 19:39: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: patch
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78870-4-Hf36tJQJ8s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03080.txt.bz2
Content-length: 190
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78870
--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
P.S. thanks to niXman for the patch that inspired the approach used.
>From gcc-bugs-return-606186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:46:55 2018
Return-Path: <gcc-bugs-return-606186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40708 invoked by alias); 31 May 2018 19:46: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 37347 invoked by uid 55); 31 May 2018 19:46:51 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85591] __builtin_cpu_is() is not detecting bdver2 with Model = 0x02
Date: Thu, 31 May 2018 19: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uros 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-85591-4-nNiBwmtqBV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03081.txt.bz2
Content-length: 447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
--- Comment #4 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu May 31 19:45:54 2018
New Revision: 261036
URL: https://gcc.gnu.org/viewcvs?rev=261036&root=gcc&view=rev
Log:
PR target/85591
* config/i386/cpuinfo.c (get_amd_cpu): Return
AMDFAM15H_BDVER2 for AMDFAM15H model 0x2.
Modified:
trunk/libgcc/ChangeLog
trunk/libgcc/config/i386/cpuinfo.c
>From gcc-bugs-return-606187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:50:30 2018
Return-Path: <gcc-bugs-return-606187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107081 invoked by alias); 31 May 2018 19:50: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 101449 invoked by uid 55); 31 May 2018 19:50:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85984] [8/9 Regression] ICE in create_pseudo_cfg, at dwarf2cfi.c:2874
Date: Thu, 31 May 2018 19: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: 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85984-4-n1gFiFrQmW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85984-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03082.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85984
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu May 31 19:49:54 2018
New Revision: 261037
URL: https://gcc.gnu.org/viewcvs?rev=261037&root=gcc&view=rev
Log:
PR target/85984
* bb-reorder.c (pass_partition_blocks::gate): Return false for
functions with naked attribute.
* gcc.target/i386/pr85984.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr85984.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/bb-reorder.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-606188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:52:26 2018
Return-Path: <gcc-bugs-return-606188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58920 invoked by alias); 31 May 2018 19:52: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 58824 invoked by uid 55); 31 May 2018 19:52:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85984] [8/9 Regression] ICE in create_pseudo_cfg, at dwarf2cfi.c:2874
Date: Thu, 31 May 2018 19: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: 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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85984-4-HSDpRHhTX5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85984-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03083.txt.bz2
Content-length: 659
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85984
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu May 31 19:51:50 2018
New Revision: 261038
URL: https://gcc.gnu.org/viewcvs?rev=261038&root=gcc&view=rev
Log:
PR target/85984
* bb-reorder.c (pass_partition_blocks::gate): Return false for
functions with naked attribute.
* gcc.target/i386/pr85984.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/pr85984.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/bb-reorder.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-606189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:54:08 2018
Return-Path: <gcc-bugs-return-606189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60770 invoked by alias); 31 May 2018 19:54: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 60434 invoked by uid 48); 31 May 2018 19:54:01 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66193] ICE for initialisation of some non-zero-sized arrays
Date: Thu, 31 May 2018 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: 5.1.1
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-66193-4-PkGlW45c0V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66193-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66193-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03084.txt.bz2
Content-length: 775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66193
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #16 from kargl at gcc dot gnu.org ---
test_case_pr66193_1_real.f90 and test_case_pr66193_2.integer.f90
compile and execute on trunk.
test_case_pr66193_3_diverse.f90 and test case pr66193_3_diverse_new.f90
still fail, because of the zero-sized nested array. Problems with
nested array constructors are tracked in a different PR. I propose
that first 2 testcases be committed to the testsuite, the 2 failing
testcase be added to the other PR, and this PR be closed.
>From gcc-bugs-return-606190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 19:58:47 2018
Return-Path: <gcc-bugs-return-606190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69854 invoked by alias); 31 May 2018 19:58: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 69191 invoked by uid 48); 31 May 2018 19:58:39 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86020] New: Performance regression in Eigen geometry.cpp test starting with r248333
Date: Thu, 31 May 2018 19: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt 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-86020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03085.txt.bz2
Content-length: 5786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
Bug ID: 86020
Summary: Performance regression in Eigen geometry.cpp test
starting with r248333
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: wschmidt at gcc dot gnu.org
Target Milestone: ---
GCC 8.1 has regressed by about 30% compared with GCC 7.3 on one of the Eigen
test cases when measured on Power9 hardware (powerpc64le-linux-gnu). Similar
performance loss is seen on Power8 hardware as well. Pat Haugen did some
bisecting and found that this began with r248334.
2017-05-22 Jan Hubicka <hubicka@ucw.cz>
* ipa-inline.c (edge_badness): Use inlined_time instead of
inline_summaries->get.
The performance difference seems to be due to a change in inlining as a result
of the above patch. The symptom is a marked increase in stack load/store
activity.
An example occurs in one of the hottest routines:
_ZN5Eigen8internal20generic_product_implINS_5BlockIKNS_6MatrixIfLi4ELi4ELi0ELi4ELi4EEELi3ELi3ELb0EEENS3_IfLi3ELi8ELi0ELi3ELi8EEENS_10DenseShapeES8_Li3EE5addToINS2_IS7_Li3ELi8ELb1EEEEEvRT_RKS6_RKS7_
Below is the code with GCC 8.1.0 :
0.15 : 1000b274: lfs f7,8(r9)
0.00 : 1000b278: li r5,2
0.00 : 1000b27c: addi r4,r1,464
0.06 : 1000b280: lfs f8,4(r9)
0.09 : 1000b284: lfs f9,0(r9)
0.00 : 1000b288: lfs f0,4(r31)
0.00 : 1000b28c: addi r3,r1,648
2.61 : 1000b290: lfs f10,32(r10)
0.71 : 1000b294: lfs f11,16(r10)
0.46 : 1000b298: lfs f12,0(r10)
1.99 : 1000b29c: fmuls f10,f10,f7
4.36 : 1000b2a0: fmadds f11,f11,f8,f10
4.20 : 1000b2a4: fmadds f12,f12,f9,f11
4.08 : 1000b2a8: fadds f0,f0,f12
7.67 : 1000b2ac: stfs f0,4(r31)
0.00 : 1000b2b0: bl 10004838
0.00 : 1000b2b4: nop
0.06 : 1000b2b8: ld r5,664(r1)
0.00 : 1000b2bc: ld r10,680(r1)
0.00 : 1000b2c0: ld r9,512(r1)
0.00 : 1000b2c4: addi r4,r1,32
0.00 : 1000b2c8: ld r6,688(r1)
0.06 : 1000b2cc: ld r7,696(r1)
0.00 : 1000b2d0: ld r8,712(r1)
0.03 : 1000b2d4: ld r0,648(r1)
0.00 : 1000b2d8: addi r3,r1,1104
0.00 : 1000b2dc: ld r11,704(r1)
0.09 : 1000b2e0: std r28,144(r1)
0.00 : 1000b2e4: std r30,152(r1)
0.00 : 1000b2e8: std r26,160(r1)
0.18 : 1000b2ec: std r5,48(r1)
0.09 : 1000b2f0: std r10,64(r1)
0.03 : 1000b2f4: ld r5,728(r1)
0.00 : 1000b2f8: ld r10,720(r1)
0.06 : 1000b2fc: std r9,136(r1)
0.00 : 1000b300: add r9,r9,r29
0.09 : 1000b304: std r0,32(r1)
0.46 : 1000b308: std r6,600(r1)
0.06 : 1000b30c: std r6,72(r1)
0.18 : 1000b310: std r7,608(r1)
0.09 : 1000b314: std r7,80(r1)
0.12 : 1000b318: std r11,88(r1)
0.40 : 1000b31c: std r9,120(r1)
0.09 : 1000b320: std r8,624(r1)
0.06 : 1000b324: std r8,96(r1)
0.03 : 1000b328: std r10,632(r1)
0.06 : 1000b32c: std r10,104(r1)
0.06 : 1000b330: std r5,112(r1)
0.15 : 1000b334: bl 1000a248 <calls the map base evaluator
function>
The additional instructions can be seen between addresses 1000b2b8 and
1000b330.
Below is the code for GCC 7.3.0 :
0.16 : 1000ac88: lfs f7,8(r9)
0.04 : 1000ac8c: ld r10,488(r1)
0.08 : 1000ac90: addi r4,r1,176
0.35 : 1000ac94: lfs f8,4(r9)
0.28 : 1000ac98: lfs f9,0(r9)
0.12 : 1000ac9c: lfs f0,0(r31)
0.00 : 1000aca0: ld r9,496(r1)
0.00 : 1000aca4: addi r3,r1,1160
3.39 : 1000aca8: lfs f10,32(r8)
0.87 : 1000acac: lfs f11,16(r8)
0.83 : 1000acb0: lfs f12,0(r8)
0.32 : 1000acb4: std r10,864(r1)
0.12 : 1000acb8: std r10,776(r1)
0.04 : 1000acbc: std r9,872(r1)
0.24 : 1000acc0: std r9,784(r1)
1.93 : 1000acc4: fmuls f10,f10,f7
4.38 : 1000acc8: fmadds f11,f11,f8,f10
5.48 : 1000accc: fmadds f12,f12,f9,f11
5.99 : 1000acd0: fadds f0,f0,f12
10.25 : 1000acd4: stfs f0,0(r31)
0.00 : 1000acd8: std r7,304(r1)
0.20 : 1000acdc: std r9,224(r1)
0.00 : 1000ace0: std r21,176(r1)
0.24 : 1000ace4: std r27,192(r1)
0.00 : 1000ace8: std r23,208(r1)
0.00 : 1000acec: std r24,232(r1)
0.04 : 1000acf0: std r26,240(r1)
0.00 : 1000acf4: std r30,248(r1)
0.12 : 1000acf8: std r26,256(r1)
0.79 : 1000acfc: std r28,264(r1)
0.16 : 1000ad00: std r25,280(r1)
0.08 : 1000ad04: std r30,288(r1)
0.28 : 1000ad08: std r29,296(r1)
0.00 : 1000ad0c: std r10,216(r1)
0.00 : 1000ad10: bl 1000aae8 <calls the map base evaluator
function>
The GCC 8.1 code has an additional call, no longer inlined, to the constructor
Eigen::Matrix(). We suspect this and similar changes in other variants of this
function are responsible.
It is hard to understand the patch that made this change out of context. I
went back to the gcc-patches mailing list to look for discussion, but I wasn't
able to find a justification for this change. Jan, could you explain its
purpose?
>From gcc-bugs-return-606191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:04:36 2018
Return-Path: <gcc-bugs-return-606191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88620 invoked by alias); 31 May 2018 20:04: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 88578 invoked by uid 48); 31 May 2018 20:04:32 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86020] Performance regression in Eigen geometry.cpp test starting with r248334
Date: Thu, 31 May 2018 20: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt 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-86020-4-i5vqRZuK70@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03086.txt.bz2
Content-length: 256
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
--- Comment #1 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Created attachment 44220
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44220&action=edit
Source file that shows the problem
>From gcc-bugs-return-606192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:06:09 2018
Return-Path: <gcc-bugs-return-606192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108092 invoked by alias); 31 May 2018 20:06: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 93610 invoked by uid 48); 31 May 2018 20:06:04 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86020] Performance regression in Eigen geometry.cpp test starting with r248334
Date: Thu, 31 May 2018 20: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.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt 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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget cc cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-86020-4-TuUNGxjtYl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03087.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |powerpc64le-linux-gnu
CC| |hubicka at gcc dot gnu.org,
| |pthaugen at gcc dot gnu.org,
| |segher at gcc dot gnu.org
Known to work| |7.3.0
Target Milestone|--- |8.2
Known to fail| |8.1.0
>From gcc-bugs-return-606193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:10:12 2018
Return-Path: <gcc-bugs-return-606193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128195 invoked by alias); 31 May 2018 20:10: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 114723 invoked by uid 55); 31 May 2018 20:10:07 -0000
From: "wilson at tuliptree dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
Date: Thu, 31 May 2018 20: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilson at tuliptree 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-86005-4-CGCA6E51uo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03088.txt.bz2
Content-length: 758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
--- Comment #6 from Jim Wilson <wilson at tuliptree dot org> ---
On Thu, 2018-05-31 at 15:07 +0000, foom at fuhm dot net wrote:
> (But also, why doesn't it implement __atomic_add_fetch inline?)
If you don't have atomic instructions, then we call an out-of-line
function that uses locks.
If you have atomic instructions, and it is a 32/64-bit operation, then
we inline it.
If you have atomic instructions, and it is a 8/16-bit operation, then
we call a lock free out-of-line function that uses a sequence of
instructions to implement it using 32/64-bit atomic instructions. And
as mentioned previously, I have an unfinished prototype patch to fix
this by emitting the sequence of instructions inline.
>From gcc-bugs-return-606194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:42:41 2018
Return-Path: <gcc-bugs-return-606194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30515 invoked by alias); 31 May 2018 20: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 28555 invoked by uid 48); 31 May 2018 20:42:36 -0000
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83026] missing strlen optimization for strcmp of unequal strings
Date: Thu, 31 May 2018 20: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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qinzhao at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: qing.zhao at oracle dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-83026-4-CAEGyIHAAc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83026-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83026-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03089.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83026
qinzhao at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qinzhao at gcc dot gnu.org
--- Comment #5 from qinzhao at gcc dot gnu.org ---
the patch has been put back into trunk as revision 261039:
https://gcc.gnu.org/viewcvs/gcc?limit_changes=0&view=revision&revision=261039
>From gcc-bugs-return-606196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:44:51 2018
Return-Path: <gcc-bugs-return-606196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36052 invoked by alias); 31 May 2018 20: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 35973 invoked by uid 48); 31 May 2018 20:44:46 -0000
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83819] [meta-bug] missing strlen optimizations
Date: Thu, 31 May 2018 20:44: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, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qinzhao 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-83819-4-ENVQcfmhic@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03091.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 83026, which changed state.
Bug 83026 Summary: missing strlen optimization for strcmp of unequal strings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83026
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-606195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:44:51 2018
Return-Path: <gcc-bugs-return-606195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36040 invoked by alias); 31 May 2018 20: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 35940 invoked by uid 48); 31 May 2018 20:44:45 -0000
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83026] missing strlen optimization for strcmp of unequal strings
Date: Thu, 31 May 2018 20: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qinzhao at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: qing.zhao at oracle dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83026-4-6wPqt4nn8h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83026-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83026-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03090.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83026
qinzhao at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from qinzhao at gcc dot gnu.org ---
the change is in trunk, I am closing this bug.
>From gcc-bugs-return-606197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 20:47:57 2018
Return-Path: <gcc-bugs-return-606197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41272 invoked by alias); 31 May 2018 20:47: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 41212 invoked by uid 48); 31 May 2018 20:47:51 -0000
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/78809] Inline strcmp with small constant strings
Date: Thu, 31 May 2018 20: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: 7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: qinzhao at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: qing.zhao at oracle dot com
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-78809-4-E0Nx0qN4o5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03092.txt.bz2
Content-length: 508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78809
qinzhao at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qinzhao at gcc dot gnu.org
--- Comment #35 from qinzhao at gcc dot gnu.org ---
the second part of the implementation is checked into gcc9 today as:
https://gcc.gnu.org/viewcvs/gcc?limit_changes=0&view=revision&revision=261039
>From gcc-bugs-return-606198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:05:00 2018
Return-Path: <gcc-bugs-return-606198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95121 invoked by alias); 31 May 2018 22:05: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 95066 invoked by uid 55); 31 May 2018 22:04:56 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85591] __builtin_cpu_is() is not detecting bdver2 with Model = 0x02
Date: Thu, 31 May 2018 22: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: uros 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-85591-4-WkIHlAJEsK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03093.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
--- Comment #5 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu May 31 22:04:22 2018
New Revision: 261042
URL: https://gcc.gnu.org/viewcvs?rev=261042&root=gcc&view=rev
Log:
PR target/85591
* config/i386/cpuinfo.c (get_amd_cpu): Return
AMDFAM15H_BDVER2 for AMDFAM15H model 0x2.
Modified:
branches/gcc-8-branch/libgcc/ChangeLog
branches/gcc-8-branch/libgcc/config/i386/cpuinfo.c
>From gcc-bugs-return-606199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:10:15 2018
Return-Path: <gcc-bugs-return-606199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98952 invoked by alias); 31 May 2018 22:10: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 98888 invoked by uid 55); 31 May 2018 22:10:11 -0000
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85950] Unsafe-math-optimizations regresses optimization using SSE4.1 roundss
Date: Thu, 31 May 2018 22: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: 8.1.1
X-Bugzilla-Keywords: missed-optimization
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85950-4-PFjMWsFgQA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03094.txt.bz2
Content-length: 848
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85950
--- Comment #8 from uros at gcc dot gnu.org ---
Author: uros
Date: Thu May 31 22:09:39 2018
New Revision: 261043
URL: https://gcc.gnu.org/viewcvs?rev=261043&root=gcc&view=rev
Log:
PR target/85950
* config/i386/i386.md (l<rounding_insn><MODEF:mode><SWI48:mode>2):
Enable for TARGET_SSE4_1 and generate rounds{s,d} and cvtts{s,d}2si{,q}
sequence.
(sse4_1_round<mode>2): Use nonimmediate_operand
for operand 1 predicate.
testsuite/ChangeLog:
PR target/85950
* gcc.target/i386/pr85950.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/pr85950.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/i386.md
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-606200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:11:05 2018
Return-Path: <gcc-bugs-return-606200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106554 invoked by alias); 31 May 2018 22:11: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 106427 invoked by uid 48); 31 May 2018 22:11:00 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85591] __builtin_cpu_is() is not detecting bdver2 with Model = 0x02
Date: Thu, 31 May 2018 22: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: 8.0.1
X-Bugzilla-Keywords:
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone
Message-ID: <bug-85591-4-KagFZJedce@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03095.txt.bz2
Content-length: 573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85591
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
Target Milestone|--- |8.2
--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
Fixed for 8.2+
>From gcc-bugs-return-606201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:12:08 2018
Return-Path: <gcc-bugs-return-606201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84642 invoked by alias); 31 May 2018 22:12: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 76787 invoked by uid 48); 31 May 2018 22:12:01 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85950] Unsafe-math-optimizations regresses optimization using SSE4.1 roundss
Date: Thu, 31 May 2018 22: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.1
X-Bugzilla-Keywords: missed-optimization
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-85950-4-lpwcnbSAw6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03096.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85950
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.2
--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> ---
Fixed for 8.2+.
>From gcc-bugs-return-606202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:16:19 2018
Return-Path: <gcc-bugs-return-606202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29209 invoked by alias); 31 May 2018 22: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 28967 invoked by uid 48); 31 May 2018 22:15:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85984] [8/9 Regression] ICE in create_pseudo_cfg, at dwarf2cfi.c:2874
Date: Thu, 31 May 2018 22: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: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85984-4-ohfruqWzk8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85984-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03097.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85984
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-606203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:47:44 2018
Return-Path: <gcc-bugs-return-606203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120616 invoked by alias); 31 May 2018 22:47: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 120541 invoked by uid 55); 31 May 2018 22:47:39 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/85429] Several gotools tests FAIL with Solaris as
Date: Thu, 31 May 2018 22:47: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85429-4-1XsdbqZU6K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03098.txt.bz2
Content-length: 6761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85429
--- Comment #12 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Thu May 31 22:46:52 2018
New Revision: 261045
URL: https://gcc.gnu.org/viewcvs?rev=261045&root=gcc&view=rev
Log:
PR go/85429
Various backports from mainline:
libgo: update to Go 1.10.2 release
cmd/go: support more Solaris assembler syntaxes
Patch by Rainer Orth.
cmd/go: update to match recent changes to gc
In https://golang.org/cl/111097 the gc version of cmd/go was updated
to include some gofrontend-specific changes. The gofrontend code
already has different versions of those changes; this CL makes the
gofrontend match the upstream code.
cmd/go, cmd/vet: make vet work with gccgo
Backport https://golang.org/cl/113715 and https://golang.org/cl/113716:
cmd/go: don't pass -compiler flag to vet
Without this running go vet -compiler=gccgo causes vet to fail.
The vet tool does need to know the compiler, but it is passed in
vetConfig.Compiler.
cmd/go, cmd/vet, go/internal/gccgoimport: make vet work with gccgo
When using gccgo/GoLLVM, there is no package file for a standard
library package. Since it is impossible for the go tool to rebuild the
package, and since the package file exists only in the form of a .gox
file, this seems like the best choice. Unfortunately it was confusing
vet, which wanted to see a real file. This caused vet to report errors
about missing package files for standard library packages. The
gccgoimporter knows how to correctly handle this case. Fix this by
1) telling vet which packages are standard;
2) letting vet skip those packages;
3) letting the gccgoimporter handle this case.
As a separate required fix, gccgo/GoLLVM has no runtime/cgo package,
so don't try to depend on it (as it happens, this fixes golang/go#25324).
The result is that the cmd/go vet tests pass when using -compiler=gccgo.
crypto/x509: specify path to AIX certificate file
go/build, cmd/go: update to match recent changes to gc
Several recent changes to the gc version of cmd/go improve the
gofrontend support. These changes are partially copies of existing
gofrontend differences, and partially new code. This CL makes the
gofrontend match the upstream code.
The changes included here come from:
https://golang.org/cl/111575
https://golang.org/cl/111595
https://golang.org/cl/111635
https://golang.org/cl/111636
For the record, the following recent gc changes are based on code
already present in the gofrontend repo:
https://golang.org/cl/110915
https://golang.org/cl/111615
For the record, a gc change, partially based on earlier gofrontend
work, also with new gc code, was already copied to gofrontend repo in
CL 111099:
https://golang.org/cl/111097
This moves the generated list of standard library packages from
cmd/go/internal/load to go/build.
gotools/ChangeLog:
Backport from mainline:
2018-05-09 Ian Lance Taylor <iant@golang.org>
* Makefile.am (check-go-tool): Don't copy zstdpkglist.go.
* Makefile.in: Rebuild.
Added:
branches/gcc-8-branch/libgo/go/cmd/internal/objabi/funcid.go
branches/gcc-8-branch/libgo/go/go/build/gc.go
branches/gcc-8-branch/libgo/go/go/build/gccgo.go
branches/gcc-8-branch/libgo/go/go/internal/srcimporter/testdata/issue23092/
branches/gcc-8-branch/libgo/go/go/internal/srcimporter/testdata/issue23092/issue23092.go
branches/gcc-8-branch/libgo/go/go/internal/srcimporter/testdata/issue24392/
branches/gcc-8-branch/libgo/go/go/internal/srcimporter/testdata/issue24392/issue24392.go
branches/gcc-8-branch/libgo/go/net/http/pprof/pprof_test.go
branches/gcc-8-branch/libgo/misc/cgo/testplugin/src/issue24351/
branches/gcc-8-branch/libgo/misc/cgo/testplugin/src/issue24351/main.go
branches/gcc-8-branch/libgo/misc/cgo/testplugin/src/issue24351/plugin.go
Modified:
branches/gcc-8-branch/gotools/ChangeLog
branches/gcc-8-branch/gotools/Makefile.am
branches/gcc-8-branch/gotools/Makefile.in
branches/gcc-8-branch/libgo/MERGE
branches/gcc-8-branch/libgo/Makefile.am
branches/gcc-8-branch/libgo/Makefile.in
branches/gcc-8-branch/libgo/VERSION
branches/gcc-8-branch/libgo/go/archive/zip/reader.go
branches/gcc-8-branch/libgo/go/archive/zip/reader_test.go
branches/gcc-8-branch/libgo/go/cmd/go/alldocs.go
branches/gcc-8-branch/libgo/go/cmd/go/go_test.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/cfg/cfg.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/get/vcs.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/get/vcs_test.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/help/helpdoc.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/load/pkg.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/test/test.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/vet/vet.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/vet/vetflag.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/work/buildid.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/work/exec.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/work/security.go
branches/gcc-8-branch/libgo/go/cmd/go/internal/work/security_test.go
branches/gcc-8-branch/libgo/go/cmd/vet/main.go
branches/gcc-8-branch/libgo/go/crypto/x509/name_constraints_test.go
branches/gcc-8-branch/libgo/go/crypto/x509/root_aix.go
branches/gcc-8-branch/libgo/go/crypto/x509/verify.go
branches/gcc-8-branch/libgo/go/crypto/x509/x509.go
branches/gcc-8-branch/libgo/go/encoding/json/decode.go
branches/gcc-8-branch/libgo/go/encoding/json/decode_test.go
branches/gcc-8-branch/libgo/go/go/build/build.go
branches/gcc-8-branch/libgo/go/go/internal/gccgoimporter/importer.go
branches/gcc-8-branch/libgo/go/go/internal/srcimporter/srcimporter.go
branches/gcc-8-branch/libgo/go/go/internal/srcimporter/srcimporter_test.go
branches/gcc-8-branch/libgo/go/internal/singleflight/singleflight.go
branches/gcc-8-branch/libgo/go/net/http/pprof/pprof.go
branches/gcc-8-branch/libgo/go/net/lookup.go
branches/gcc-8-branch/libgo/go/net/lookup_test.go
branches/gcc-8-branch/libgo/go/net/tcpsock_unix_test.go
branches/gcc-8-branch/libgo/go/runtime/error.go
branches/gcc-8-branch/libgo/go/runtime/panic.go
branches/gcc-8-branch/libgo/go/runtime/proc.go
branches/gcc-8-branch/libgo/go/runtime/symtab.go
branches/gcc-8-branch/libgo/misc/cgo/testplugin/test.bash
branches/gcc-8-branch/libgo/misc/cgo/testshared/shared_test.go
>From gcc-bugs-return-606204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 31 22:50:43 2018
Return-Path: <gcc-bugs-return-606204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123033 invoked by alias); 31 May 2018 22:50: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 122960 invoked by uid 55); 31 May 2018 22:50:38 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85957] i686: Integers appear to be different, but compare as equal
Date: Thu, 31 May 2018 22: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: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery 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-85957-4-8SHEstAYAM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg03099.txt.bz2
Content-length: 860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85957
--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Mon, 28 May 2018, vincent-gcc at vinc17 dot net wrote:
> floating-point expression: Once a floating-point number has been converted into
> an integer type, the value of this integer must be fixed.
Yes, I agree that any particular conversion to integer executed in the
abstract machine must produce some definite integer value for each
execution.
(Conversions of *out-of-range* floating-point values to integer are a
trickier case; under Annex F they produce unspecified values. I think
semantics along the lines of N2221 are fine for unspecified values arising
from reading an uninitialized object, but more questionable for values
arising from a floating-point-to-integer conversion.)
>From gcc-bugs-return-606205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 02:16:25 2018
Return-Path: <gcc-bugs-return-606205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4372 invoked by alias); 1 Jun 2018 02:16: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 4250 invoked by uid 55); 1 Jun 2018 02:16:06 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Fri, 01 Jun 2018 02:16: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: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85840-4-SVuGtEerOp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00000.txt.bz2
Content-length: 617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
--- Comment #15 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Fri Jun 1 02:14:53 2018
New Revision: 261054
URL: https://gcc.gnu.org/viewcvs?rev=261054&root=gcc&view=rev
Log:
2018-05-31 Jerry DeLisle <jvdelisle@gcc.gnu.org>
Backport from trunk.
PR libgfortran/85840
* io/write.c (write_real, write_real_g0, write_complex): Use
separate local variables for the float string length.
Modified:
branches/gcc-8-branch/libgfortran/ChangeLog
branches/gcc-8-branch/libgfortran/io/write.c
>From gcc-bugs-return-606206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 03:21:59 2018
Return-Path: <gcc-bugs-return-606206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30534 invoked by alias); 1 Jun 2018 03:21: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 30458 invoked by uid 48); 1 Jun 2018 03:21:53 -0000
From: "john.harper at vuw dot ac.nz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86021] New: ICE when initializing a character array
Date: Fri, 01 Jun 2018 03:21: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: 7.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: john.harper at vuw dot ac.nz
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-86021-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00001.txt.bz2
Content-length: 2060
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86021
Bug ID: 86021
Summary: ICE when initializing a character array
Product: gcc
Version: 7.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: john.harper at vuw dot ac.nz
Target Milestone: ---
On compiling this program with gfortran 7.2.1 the error message below it
appears. Is it a duplicate of bug 68155?
cayley[~/Jfh] % cat gfbug8.f90
program testgf
implicit none
integer,parameter:: mp=selected_real_kind(14)
real(mp):: x
character(precision(x)+5)::labels(3)=['my series ','intrinsic ','difference']
print *,labels
end program testgf
cayley[~/Jfh] % gfortran gfbug8.f90
gfbug8.f90:7:0:
end program testgf
internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
cayley[~/Jfh] % gfortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/7.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --enable-multilib --disable-werror
--enable-checking=release --enable-default-pie --enable-default-ssp
Thread model: posix
gcc version 7.2.1 20180116 (GCC)
cayley[~/Jfh] %
>From gcc-bugs-return-606207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 04:15:45 2018
Return-Path: <gcc-bugs-return-606207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87903 invoked by alias); 1 Jun 2018 04:15: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 87752 invoked by uid 89); 1 Jun 2018 04:15:27 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=none autolearn=unavailable version=3.3.2 spammyX-HELO: knxa.com
Received: from 98.15.61.117.broad.js.dynamic.163data.com.cn (HELO knxa.com) (117.61.15.98) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Jun 2018 04:15:05 +0000
Received: from PC201207261051 ([127.0.0.1]) by localhost via TCP with ESMTPA; Fri, 01 Jun 2018 12:14:35 +0800
MIME-Version: 1.0
From: =?utf-8?Q?陈�= <494620206@qq.com>
To: gcc-bugs@gcc.gnu.org
Reply-To: =?utf-8?Q?陈�= <494620206@qq.com>
Date: Fri, 01 Jun 2018 04:15:00 -0000
Subject: =?utf-8?B?5YWo5Zu96YCa55+l5ZCE5YWs5Y+45Lul5LiL5oOF5Ya1MjAxOC82LzE=?Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-SW-Source: 2018-06/txt/msg00002.txt.bz2
Content-length: 663
5pys5YWs5Y+45piv5YWo5Zu956iO5Yqh5oC76YOo5Luj5byA5Y+R56Wo5pyN
5YqhDQrjgJDlp5PlkI3jgJHvvJrpmYjkuK3jgJDlhazlj7jjgJHvvJrnqI7l
iqHlkqjor6LmnI3liqHjgJDogYzkvY3jgJHvvJrnu4/nkIbjgJDnu4/okKXo
jIPlm7TjgJHvvJrkvIHkuJrnqI7liqHlkqjor6Iu5ZCE5YWs5Y+456iO5Yqh
5ZKo6K+iLuWQhOihjOS4mueojuWKoeWSqOivoi7kuKrkurrnqI7liqHlkqjo
r6LigKbmma7pgJrku6Xlj4rkuJPnlKglMTcuJS8lM+etieetieOAguS4uuWk
p+WutuaWueS+v++8iOS7o+W8gOWPkeelqO+8ieacjeWKoeOAguWmgueUqOaJ
k+aJsOS4jeWlveaEj+aAne+8jOelneaCqOeUn+a0u+aEieW/q+OAgg0K44CQ
6K+a5L+h5Lqk5rWB44CR77ya5Y+R56Wo5L+d55yf772e6aqM5ZCO5LuY5qy+
44CC44CQ6IGU57O75pa55byP44CR77ya5b6u5L+hQTEzNjg5MDAxNTAz44CQ
UVE0OTQ2MjAyMDbnlLXor50xMzA1NDA3MjU1MuOAkQ0KJm5ic3A7
>From gcc-bugs-return-606208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 04:51:08 2018
Return-Path: <gcc-bugs-return-606208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67177 invoked by alias); 1 Jun 2018 04:51: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 65038 invoked by uid 48); 1 Jun 2018 04:51:02 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66159] bogus warning for alias-declaration using elaborated-type-specifier
Date: Fri, 01 Jun 2018 04: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: 5.0
X-Bugzilla-Keywords: diagnostic
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-66159-4-jRZojw0tdK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66159-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66159-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00003.txt.bz2
Content-length: 2735
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66159
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> Patch for stage 1:
>
> diff --git a/gcc/cp/parser.c b/gcc/cp/parser.c
> index 4fa546a086c..4dc4e751b28 100644
> --- a/gcc/cp/parser.c
> +++ b/gcc/cp/parser.c
> @@ -17818,9 +17818,11 @@ cp_parser_elaborated_type_specifier (cp_parser*
> parser,
> caught elsewhere in parsing. Those that are pointless arrive
> here. */
>
> - if (cp_lexer_next_token_is (parser->lexer, CPP_SEMICOLON)
> + if (warn_redundant_decls
> + && cp_lexer_next_token_is (parser->lexer, CPP_SEMICOLON)
> && !is_friend && !processing_explicit_instantiation)
> - warning (0, "declaration %qD does not declare anything", decl);
> + warning (OPT_Wredundant_decls,
> + "declaration %qD does not declare anything", decl);
>
> type = TREE_TYPE (decl);
> }
> diff --git a/gcc/testsuite/g++.dg/warn/forward-inner.C
> b/gcc/testsuite/g++.dg/warn/forward-inner.C
> index 5336d4ed946..f720a6cdae3 100644
> --- a/gcc/testsuite/g++.dg/warn/forward-inner.C
> +++ b/gcc/testsuite/g++.dg/warn/forward-inner.C
> @@ -1,5 +1,6 @@
> // Check that the compiler warns about inner-style forward declarations in
> // contexts where they're not actually illegal, but merely useless.
> +// { dg-options "-Wredundant-decls" }
>
> // Verify warnings for and within classes, and by extension, struct and
> union.
> class C1;
> @@ -70,7 +71,7 @@ template class TC6<int>::TC7; // Valid explicit
> instantiation, no warning
>
>
> // Verify that friend declarations, also easy to confuse with forward
> -// declrations, are similarly not warned about.
> +// declarations, are similarly not warned about.
> class C8 {
> public:
> class C9 { };
> @@ -79,3 +80,10 @@ class C10 {
> public:
> friend class C8::C9; // Valid friend declaration, no warning
> };
> +
> +#if __cplusplus >= 201103L
> +// Verify that alias-declarations using an elaborated-type-specifier and
> +// nested-name-specifier are not warned about (PR c++/66159).
> +struct C11;
> +using A1 = struct ::C11;
> +#endif
> diff --git a/gcc/testsuite/g++.dg/warn/pr36999.C
> b/gcc/testsuite/g++.dg/warn/pr36999.C
> index ce2286efcf4..6f69e192d02 100644
> --- a/gcc/testsuite/g++.dg/warn/pr36999.C
> +++ b/gcc/testsuite/g++.dg/warn/pr36999.C
> @@ -1,5 +1,6 @@
> /* PR36999: Erroneous "does not declare anything" warnings. */
> /* { dg-do compile } */
> +/* { dg-options "-Wredundant-decls" } */
>
> class C1 {
> public: class C2 { };
It's stage 1 now.
>From gcc-bugs-return-606209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 07:18:02 2018
Return-Path: <gcc-bugs-return-606209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49188 invoked by alias); 1 Jun 2018 07:18: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 49117 invoked by uid 48); 1 Jun 2018 07:17:51 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/49611] Inline asm should support input/output of flags
Date: Fri, 01 Jun 2018 07:18: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.5.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ubizjak 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-49611-4-7EyxUwDOgM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00004.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49611
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to David from comment #16)
> Still, if I were Richard, I'd be closing this bug. If someone has
> optimization issues with his solution, that's a new bug.
This was implemented some time ago.
>From gcc-bugs-return-606210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 07:37:31 2018
Return-Path: <gcc-bugs-return-606210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77650 invoked by alias); 1 Jun 2018 07: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 77544 invoked by uid 48); 1 Jun 2018 07:37:24 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85774] Incorrect stack-use-after-scope caused by missing cleanup of shadow bytes
Date: Fri, 01 Jun 2018 07:37: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.1.1
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-85774-4-KOTQiFriFb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00005.txt.bz2
Content-length: 336
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85774
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #6)
> (In reply to Jakub Jelinek from comment #5)
> > If the variable is unused, why is any stack assigned to it?
>
> I guess it's due to -O0 or am I wrong?
Jakub?
>From gcc-bugs-return-606211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 07:50:40 2018
Return-Path: <gcc-bugs-return-606211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122333 invoked by alias); 1 Jun 2018 07:50: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 122275 invoked by uid 48); 1 Jun 2018 07:50:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86003] [8/9 Regression] GCC fails to build when configured --with-cpu=xscale
Date: Fri, 01 Jun 2018 07: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: 8.1.0
X-Bugzilla-Keywords: build
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget priority target_milestone
Message-ID: <bug-86003-4-DYjjTA1Wew@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00006.txt.bz2
Content-length: 398
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86003
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |arm
Priority|P3 |P2
Target Milestone|--- |8.2
>From gcc-bugs-return-606212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 07:52:06 2018
Return-Path: <gcc-bugs-return-606212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125398 invoked by alias); 1 Jun 2018 07:52: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 124381 invoked by uid 48); 1 Jun 2018 07:52:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86004] [9 regression] Several lto test cases begin failing with r260963
Date: Fri, 01 Jun 2018 07:52: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: 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: target_milestone
Message-ID: <bug-86004-4-THVNBWnweW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86004-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00007.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86004
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Do we somehow rely on plugin auto-loading now?
>From gcc-bugs-return-606213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 07:58:55 2018
Return-Path: <gcc-bugs-return-606213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82815 invoked by alias); 1 Jun 2018 07:58: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 82756 invoked by uid 48); 1 Jun 2018 07:58:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86007] precompiled header on bdver2 with -march=native triggers a "created and used with differing settings of '-mlwp'" warning, intermittently
Date: Fri, 01 Jun 2018 07: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: 8.1.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: cf_gcctarget component
Message-ID: <bug-86007-4-tvAzpgaIiO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00008.txt.bz2
Content-length: 667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86007
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*, i?86-*-*
Component|pch |target
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
It sounds like -mlwp is detected randomly..
On current trunk I get it consistently detected when doing
> gcc -S t.c -march=native -v 2>&1 | grep lwp | sed -e 's/.*\(-m\(no-\)\?lwp\).*/\1/'
repeatedly on a simple empty input.
>From gcc-bugs-return-606214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:03:41 2018
Return-Path: <gcc-bugs-return-606214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104142 invoked by alias); 1 Jun 2018 08:03: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 104069 invoked by uid 48); 1 Jun 2018 08:03:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86010] [7/8/9 Regression] redundant memset with smaller size not eliminated
Date: Fri, 01 Jun 2018 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: 8.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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone short_desc everconfirmed
Message-ID: <bug-86010-4-aRDOfw1Ini@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00009.txt.bz2
Content-length: 1165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86010
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-06-01
CC| |law at gcc dot gnu.org
Known to work| |4.8.5
Target Milestone|--- |7.4
Summary|[7/8 Regression] redundant |[7/8/9 Regression]
|memset with smaller size |redundant memset with
|not eliminated |smaller size not eliminated
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
This is the new byte-tracking in DSE I presume which isn't able to prune
optimally (off-by-one?) or do the better thing, namely removing the
later memset instead of the earlier. With GCC 4.8 we managed to combine
the memsets at the RTL level.
>From gcc-bugs-return-606215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:04:47 2018
Return-Path: <gcc-bugs-return-606215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105823 invoked by alias); 1 Jun 2018 08: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 105787 invoked by uid 48); 1 Jun 2018 08:04:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86011] Inefficient code generated for ldivmod with constant value
Date: Fri, 01 Jun 2018 08: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: 7.2.0
X-Bugzilla-Keywords: missed-optimization
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: keywords cf_gcctarget bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-86011-4-Po6rF3TAfw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86011-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86011-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00010.txt.bz2
Content-length: 706
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86011
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |arm
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-06-01
Component|other |target
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think this was fixed with GCC 8. Can you check?
>From gcc-bugs-return-606216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:06:51 2018
Return-Path: <gcc-bugs-return-606216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110691 invoked by alias); 1 Jun 2018 08:06: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 110629 invoked by uid 48); 1 Jun 2018 08:06:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86013] std::vector::shrink_to_fit() could sometimes use realloc()
Date: Fri, 01 Jun 2018 08:06: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.1.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
Message-ID: <bug-86013-4-BsBKDl6oHT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00011.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86013
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I wonder if technically shrink_to_fit() is allowed to elide the shrinking? And
yes, I'm equally shocked about the need to copy!
>From gcc-bugs-return-606217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:16:14 2018
Return-Path: <gcc-bugs-return-606217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33575 invoked by alias); 1 Jun 2018 08:16: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 33272 invoked by uid 48); 1 Jun 2018 08:15:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86017] multiple consecutive calls to bzero/memset not merged
Date: Fri, 01 Jun 2018 08: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.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: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-86017-4-KG4Wxnc8Zf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86017-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00012.txt.bz2
Content-length: 710
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86017
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-06-01
Assignee|unassigned 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. A related issue is that we inline the first but not the adjacent
memsets. Fixing that makes us apply store-merging. Testing a patch.
>From gcc-bugs-return-606218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:20:46 2018
Return-Path: <gcc-bugs-return-606218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59676 invoked by alias); 1 Jun 2018 08:20: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 59618 invoked by uid 55); 1 Jun 2018 08:20:41 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85960] -fipa-pta and ifunc are incompatible
Date: Fri, 01 Jun 2018 08:20: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.1.1
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:
Message-ID: <bug-85960-4-JVFd6uTFXi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00013.txt.bz2
Content-length: 1054
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85960
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri Jun 1 08:20:08 2018
New Revision: 261056
URL: https://gcc.gnu.org/viewcvs?rev=261056&root=gcc&view=rev
Log:
2018-06-01 Richard Biener <rguenther@suse.de>
PR ipa/85960
* tree-ssa-structalias.c (get_function_part_constraint):
Handle NULL fi->decl.
(find_func_aliases_for_call): Properly handle indirect
fi from direct call.
(find_func_clobbers): Likewise.
(ipa_pta_execute): Likewise.
(create_variable_info_for): For functions that are ifunc_resolver
resolve to a varinfo that contains the result of the resolver
call.
(associate_varinfo_to_alias): Do not treat ifunc resolvers as
aliases.
* gcc.dg/ipa/ipa-pta-19.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/ipa/ipa-pta-19.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-structalias.c
>From gcc-bugs-return-606219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:25:13 2018
Return-Path: <gcc-bugs-return-606219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91154 invoked by alias); 1 Jun 2018 08:25: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 90980 invoked by uid 48); 1 Jun 2018 08:25:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86013] std::vector::shrink_to_fit() could sometimes use realloc()
Date: Fri, 01 Jun 2018 08: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: 8.1.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-86013-4-NXSMhruBB7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86013-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00014.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86013
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
shrink_to_fit is a non-binding request, the implementation is allowed to
completely ignore it. But the expected semantics (at least, expected by those
who designed the feature) is that it reallocates new storage, copies the
elements, and deallocates the old storage. If you don't want that, don't call
shrink_to_fit.
I don't see how this qualifies as a missed-optimization when doing it is
impossible in the general case.
>From gcc-bugs-return-606220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:25:15 2018
Return-Path: <gcc-bugs-return-606220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91431 invoked by alias); 1 Jun 2018 08: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 91053 invoked by uid 48); 1 Jun 2018 08:25:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85960] -fipa-pta and ifunc are incompatible
Date: Fri, 01 Jun 2018 08: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: 8.1.1
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: cf_known_to_work cf_known_to_fail
Message-ID: <bug-85960-4-17tqgX5Rq4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00015.txt.bz2
Content-length: 733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85960
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |9.0
Known to fail| |8.1.0
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar. As it is unlikely a regression I'm only considering a
backport to GCC 8 but also only after some soaking on trunk.
Gianni - can you put the fix (that was actually committed, it has some
fixed over the attached patch) on more testing on your code? It should
trivially apply to GCC 8 as well.
>From gcc-bugs-return-606221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:32:03 2018
Return-Path: <gcc-bugs-return-606221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124204 invoked by alias); 1 Jun 2018 08:32: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 124119 invoked by uid 48); 1 Jun 2018 08:31:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86021] ICE when initializing a character array
Date: Fri, 01 Jun 2018 08: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: 7.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: 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-86021-4-PznUdc57hG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86021-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86021-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00016.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86021
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Both look more like PR84141/PR84155. Paul, the gfc_get_dtype changes should
probably be backported.
>From gcc-bugs-return-606222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:34:58 2018
Return-Path: <gcc-bugs-return-606222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66659 invoked by alias); 1 Jun 2018 08:34: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 64230 invoked by uid 48); 1 Jun 2018 08:34:51 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85964] [8/9 Regression] compile time hog w/ -O3 -ftracer -fno-guess-branch-probability
Date: Fri, 01 Jun 2018 08: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: 8.1.0
X-Bugzilla-Keywords: compile-time-hog
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85964-4-4ykM68dzq0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85964-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00017.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85964
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
Jeff can you look at the backwards threading scaling issue? There's also
PR69580
for that which may be the same underlying issue.
>From gcc-bugs-return-606223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:36:02 2018
Return-Path: <gcc-bugs-return-606223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75177 invoked by alias); 1 Jun 2018 08:36: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 75097 invoked by uid 48); 1 Jun 2018 08:35:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86019] [8/9 Regression] Unref implementation using atomic_thread_fence generates worse code on x86-64 in gcc 8.1 than 7.3
Date: Fri, 01 Jun 2018 08: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: 8.1.0
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_file_loc cf_known_to_work version target_milestone short_desc
Message-ID: <bug-86019-4-HAzpS8TyDP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86019-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86019-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00018.txt.bz2
Content-length: 882
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86019
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
URL|missed-optimization |
Known to work| |7.3.0
Version|unknown |8.1.0
Target Milestone|--- |8.2
Summary|Unref implementation using |[8/9 Regression] Unref
|atomic_thread_fence |implementation using
|generates worse code on |atomic_thread_fence
|x86-64 in gcc 8.1 than 7.3 |generates worse code on
| |x86-64 in gcc 8.1 than 7.3
>From gcc-bugs-return-606224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 08:49:55 2018
Return-Path: <gcc-bugs-return-606224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103651 invoked by alias); 1 Jun 2018 08:49: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 103451 invoked by uid 48); 1 Jun 2018 08:49:37 -0000
From: "m.schewe at apt dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60410] [4.9/5/6 Regression] -fshort-double ICEs x86_64
Date: Fri, 01 Jun 2018 08: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: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m.schewe at apt dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: bernds at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60410-4-uJwPdHP0eu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60410-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60410-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00019.txt.bz2
Content-length: 1094
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60410
--- Comment #20 from M.Schewe <m.schewe at apt dot de> ---
Removing -fshort-double completely was not a good idea.
It is required for ARM microcontrollers, e.g. ARM Cortex M4F with a FPU which
can handly only single precision arithmetic operations. All double precision
arithmetics must be emulated by slow integer software.
Without this option it is no more possible to compile runtime libraries and
application to efficiently use this FPU.
Restricing resolution to single precision is acceptable for many embedded
realtime applications, often runtime requirements must be met.
I agree to you that on architectures with powerful FPUs like x86 and x86_64
this option is not so important and may be unsupported to solve bugs.
I suggest to revert the changes from rev. 233218 thus implementing
-fshort-double as before.
Architectures which have implementation-bugs like x86_64-*-* simply can abort
compilation if the option is activated with some error message saying
"-fshort-double option is no more supported on this archeticture".
>From gcc-bugs-return-606225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 09:02:38 2018
Return-Path: <gcc-bugs-return-606225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66289 invoked by alias); 1 Jun 2018 09:02: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 65970 invoked by uid 48); 1 Jun 2018 09:02:24 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86021] ICE when initializing a character array
Date: Fri, 01 Jun 2018 09:02: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.2.1
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86021-4-ED8FEST9mF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86021-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86021-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-06/txt/msg00020.txt.bz2
Content-length: 323
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86021
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> Both look more like PR84141/PR84155. Paul, the gfc_get_dtype changes should
> probably be backported.
I'll take a look see over the weekend.
Cheers
Paul
>From gcc-bugs-return-606227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 01 09:03:32 2018
Return-Path: <gcc-bugs-return-606227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77133 invoked by alias); 1 Jun 2018 09: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 76714 invoked by uid 89); 1 Jun 2018 09:03:20 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.8 required=5.0 testsºYES_50,HTML_MESSAGE,SEM_URIRED,SPF_PASS,T_REMOTE_IMAGE autolearn=no version=3.3.2 spammy=culture, Hx-languages-length:4551, economy, Engineering
X-HELO: fencepost.gnu.org
Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (208.118.235.10) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Jun 2018 09:03:17 +0000
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43238) by fencepost.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <member@ijaaa.org>) id 1fOfxq-0006AY-RQ for bug-gcc@gnu.org; Fri, 01 Jun 2018 05:03:15 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <member@ijaaa.org>) id 1fOfxp-0001Gg-FM for bug-gcc@gnu.org; Fri, 01 Jun 2018 05:03:14 -0400
Received: from mail-pf0-x241.google.com ([2607:f8b0:400e:c00::241]:40278) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from <member@ijaaa.org>) id 1fOfxp-0001GI-3x for bug-gcc@gnu.org; Fri, 01 Jun 2018 05:03:13 -0400
Received: by mail-pf0-x241.google.com with SMTP id f189-v6so12210205pfa.7 for <bug-gcc@gnu.org>; Fri, 01 Jun 2018 02:03:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d\x1e100.net; s 161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=nIxctbbmO7jlTjLaNN1MsVtg2GhjKWkyrZpwo+C8tBQ=; b=Z2Z8HcLud8oehg+cEFes7YNgjlkqAwGhz5K2/imjJilpp9DdMmosBhukVTVE6scj1S 2Ivv0veabCskn0zehJWbBZdeO4OVEZ2CICnSPjj4Gl71OLVOdcdH4J6TYesbKD2XZ1Un ZfUyjHYmSiA+yLdwLSDpT3yg7UP7mSa9PKelsSdGvMoFnL6/0TCQM+IX7NssFyXGSn0B NHoQH0fpfoYosf1pgP6cmvazE9LMHMMgYIU/pLVxKPg4KVQgq7w+iObb7iwQBOTvBBvQ KyH7WyXx4GucQ+GQm2WuLBRdpCfCN6sDETYV0SPLBASxwrdN9bYh0H0FIs1cHKODoM9u JHpw=X-Gm-Message-State: ALKqPwcE973mkplSU8fW8ciAeHdDhdW6tDROgo4EWz/DJMJhflDgyA2w CFO3zo7MJNdZV0UqOq00TjLF8bbI6vAf9x2ZzAeh/cJv
X-Google-Smtp-Source: ADUXVKKeS77r64h+kz/YVZZdtgHY/j5eQjqSfkdC8jKAKw6liDM2/nIkVzxJBKB18j8jzQHg5AoDJ6VsdTF70svJdq0X-Received: by 2002:a62:3c96:: with SMTP id b22-v6mr5244088pfk.235.1527843791386; Fri, 01 Jun 2018 02:03:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:8084:0:0:0:0 with HTTP; Fri, 1 Jun 2018 02:03:11 -0700 (PDT)
From: Journal IJAAA <member@ijaaa.org>
Date: Fri, 01 Jun 2018 09:03:00 -0000
Message-ID: <CAHWvmG3pwArhakgAn0fT6dA0t8YX0ZZfVaYjJoQt1F+hTDy=KA@mail.gmail.com>
Subject: Join SciencePG as editorial board members/reviewers and submit your article
To: bug-gcc@gnu.org
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From: 2607:f8b0:400e:c00::241
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2018-06/txt/msg00022.txt.bz2
Content-length: 2277
<http://www.ajtte.org/home>
Dear Professor/Scholar,
We publish peer-reviewed scientific journals devoted to the development of
innovative science and technology. Now we sincerely invite scholars and
researchers to submit papers to the journals or to join in the editorial
board/reviewer team.
Submitting Your New Manuscripts
If you have burst out some new ideas in your specialized or interested
field, welcome to submit your papers to the corresponding Journals or
Special Issues so as to share your ideas with people around the world.
Joining in the Editorial Board
For the purpose of making editorial board and reviewer group expanded, we
would like to invite you to be the editorial member or reviewer of our
journals with great sincerity. If you want to know more details of the
Benefits and Responsibilities of the editorial member or reviewer, please
visit the following link: http://www.ajtte.org/journals
Open Access (OA)
Each journal uses the Open Access policy. The papers of the authors can be
cited and read widely, which can contribute to the recognition of the
authors in the certain field and beyond.
30-60 Days Fast Publication
Fast publication promotes scientific research and saves author's time,
which will make your paper to be known by people as fast as possible. The
normal time is 40-60 days after you submit your paper to our journals.
Indexing and Abstracting
Most of journals in our platform can be searched by JournalSeek, Electronic
Journals Library (EJL), WorldCat, CrossRef, Zeitschriftendatenbank, EZB,
Academickeys, ResearchBib, Polish Scholarly Bibliography, CNKI, etc.
Peer-reviewed Policy
Papers submitted to the journals are peer-reviewed, which means reviewer
anonymity allows for impartial decisions - the reviewers will not be
influenced by the authors.
Some Recommended Journals:
1. Science Journal of Analytical Chemistry
2. International Journal of Education, Culture and Society
3. International Journal of Science, Technology and Society
4. American Journal of Life Sciences
5. International Journal of Nutrition and Food Sciences
6. International Journal of Energy and Power Engineering
7. American Journal of Theoretical and Applied Statistics
8. International Journal of Economy, Energy and Environment
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences
[not found] <bug-86005-4@http.gcc.gnu.org/bugzilla/>
2018-05-31 5:53 ` [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences andrew at sifive dot com
@ 2023-07-07 16:22 ` patrick at rivosinc dot com
1 sibling, 0 replies; 2+ messages in thread
From: patrick at rivosinc dot com @ 2023-07-07 16:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005
Patrick O'Neill <patrick at rivosinc dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrick at rivosinc dot com
--- Comment #11 from Patrick O'Neill <patrick at rivosinc dot com> ---
The Char example from this issue is resolved on trunk since we added inline
subword atomics.
https://inbox.sourceware.org/gcc-patches/20230418214124.2446642-1-patrick@rivosinc.com/
Char example: https://godbolt.org/z/h94PT7hfo
char atomic(char *i) {
char j = __atomic_add_fetch(i, 1, __ATOMIC_SEQ_CST);
char k;
__atomic_load(i, &k, __ATOMIC_SEQ_CST);
return j+k;
}
options: -O3 -march=rv64iad
atomic(char*):
andi a4,a0,3
slliw a4,a4,3
li a3,255
sllw a3,a3,a4
li a1,1
andi a2,a0,-4
not a6,a3
sllw a1,a1,a4
1:
lr.w.aqrl a5, 0(a2)
add a7, a5, a1
and a7, a7, a3
and t1, a5, a6
or t1, t1, a7
sc.w.rl a7, t1, 0(a2)
bnez a7, 1b
sraw a5,a5,a4
addiw a5,a5,1
andi a5,a5,0xff
fence rw,rw
lbu a0,0(a0)
fence rw,rw
add a0,a0,a5
andi a0,a0,0xff
ret
The initial example's behavior is still present.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-07-07 16:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-86005-4@http.gcc.gnu.org/bugzilla/>
2018-05-31 5:53 ` [Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences andrew at sifive dot com
2023-07-07 16:22 ` patrick at rivosinc dot com
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).