public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128
[not found] <bug-85381-4@http.gcc.gnu.org/bugzilla/>
@ 2018-04-21 10:10 ` vries at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: vries at gcc dot gnu.org @ 2018-04-21 10:10 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: 67665 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |openacc
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
I've committed this workaround:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=b957d7c71a0a8984a88f5bfccf5a4b6fd080c47d
:
...
[nvptx, openacc] Don't emit barriers for empty loops
2018-04-21 Tom de Vries <tom@codesourcery.com>
PR target/85381
* config/nvptx/nvptx.c (nvptx_process_pars): Don't emit barriers for
empty loops.
* testsuite/libgomp.oacc-c-c++-common/pr85381-2.c: New test.
* testsuite/libgomp.oacc-c-c++-common/pr85381-3.c: New test.
* testsuite/libgomp.oacc-c-c++-common/pr85381-4.c: New test.
* testsuite/libgomp.oacc-c-c++-common/pr85381-5.c: New test.
* testsuite/libgomp.oacc-c-c++-common/pr85381.c: New test.
...
Submitted here: https://gcc.gnu.org/ml/gcc-patches/2018-04/msg01023.html .
This fixes the hang that I observed, so I'm closing this PR.
[ If nvidia comes back with a clear workaround description, I'll implement
that, but there's no point in keeping the PR open. ]
>From gcc-bugs-return-602337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 10:29:57 2018
Return-Path: <gcc-bugs-return-602337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114034 invoked by alias); 21 Apr 2018 10:29:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113958 invoked by uid 48); 21 Apr 2018 10:29:51 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/79985] ICE in code_motion_path_driver, at sel-sched.c:6580
Date: Sat, 21 Apr 2018 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amonakov at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79985-4-spI93woTQS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79985-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02461.txt.bz2
Content-length: 1099
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79985
--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Unfortunately the above doesn't fully address the issue, as schedulers and
other passes still have no idea that DF makes those assumptions and will allow
reordering of asms:
register int r asm("ebx");
int f(int x, int y)
{
int t = x/y/r;
asm("#asm" );
return t-x;
}
_Z1fii:
#APP
#asm
#NO_APP
movl %edi, %eax
cltd
idivl %esi
cltd
idivl %ebx
subl %edi, %eax
ret
See how the asm is first, even though from DF point of view it should remain
after the read of %ebx for division by r; here cprop_hardreg makes the
offending propagation.
So currently GCC has a rather split personality when it comes to deps w.r.t
global reg vars in asm statements. The documentation should spell out the
intended behavior. My suggestion is to require that references are exposed to
the compiler via constraints, allowing to remove the ad-hoc treatment in DF. I
intend to do that early in stage 1.
>From gcc-bugs-return-602338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 11:01:42 2018
Return-Path: <gcc-bugs-return-602338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81418 invoked by alias); 21 Apr 2018 11:01: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 81371 invoked by uid 48); 21 Apr 2018 11:01:37 -0000
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85423] [8 Regression] ICE in code_motion_process_successors, at sel-sched.c:6403
Date: Sat, 21 Apr 2018 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abel at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: abel at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-85423-4-4ZkUMxyEQs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02462.txt.bz2
Content-length: 1252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85423
Andrey Belevantsev <abel at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |abel at gcc dot gnu.org
--- Comment #4 from Andrey Belevantsev <abel at gcc dot gnu.org> ---
Sigh, I've put the condition that was too broad in the previous patch and also
allowed some legitimate dependencies between debug insns (so Alex was kind of
right when he expressed his concern). I'm testing the following after checking
that all of the previous PRs and this one passes:
diff --git a/gcc/sel-sched-ir.c b/gcc/sel-sched-ir.c
index ee970522890..85ff5bd3eb4 100644
--- a/gcc/sel-sched-ir.c
+++ b/gcc/sel-sched-ir.c
@@ -3308,7 +3308,7 @@ has_dependence_note_dep (insn_t pro, ds_t ds
ATTRIBUTE_UNUSED)
that a bookkeeping copy should be movable as the original insn.
Detect that here and allow that movement if we allowed it before
in the first place. */
- if (DEBUG_INSN_P (real_con)
+ if (DEBUG_INSN_P (real_con) && !DEBUG_INSN_P (real_pro)
&& INSN_UID (NEXT_INSN (pro)) == INSN_UID (real_con))
return;
>From gcc-bugs-return-602339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 11:38:22 2018
Return-Path: <gcc-bugs-return-602339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20632 invoked by alias); 21 Apr 2018 11:38: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 20571 invoked by uid 48); 21 Apr 2018 11:38:18 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85490] New: Missing STAGE4_CFLAGS in bootstrap-cet.mk
Date: Sat, 21 Apr 2018 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc blocked target_milestone cf_gcctarget
Message-ID: <bug-85490-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02463.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85490
Bug ID: 85490
Summary: Missing STAGE4_CFLAGS in bootstrap-cet.mk
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: igor.v.tsimbalist at intel dot com
Blocks: 81652
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
Since profiledbootstrap uses
STAGEfeedback_CFLAGS = $(STAGE4_CFLAGS) -fprofile-use
bootstrap-cet.mk should define STAGE4_CFLAGS to support profiledbootstrap
with CET.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81652
[Bug 81652] [meta-bug] -fcf-protection=full bugs
>From gcc-bugs-return-602340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 12:20:35 2018
Return-Path: <gcc-bugs-return-602340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26992 invoked by alias); 21 Apr 2018 12:20:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26316 invoked by uid 48); 21 Apr 2018 12:20:30 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68933] ICE when mixing "-fprofile-arcs -ftest-coverage" and "-fcoarray=lib" on gcc-6 only
Date: Sat, 21 Apr 2018 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.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:
Message-ID: <bug-68933-4-qlE4AT0N7h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02464.txt.bz2
Content-length: 156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68933
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
It seems to work with 7.3.0.
>From gcc-bugs-return-602341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 12:29:17 2018
Return-Path: <gcc-bugs-return-602341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43359 invoked by alias); 21 Apr 2018 12:29: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 43283 invoked by uid 48); 21 Apr 2018 12:29:12 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67076] [6/7/8 Regression] [F08] Critical inside a module procedure
Date: Sat, 21 Apr 2018 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.2.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: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-67076-4-KvirUZyT2x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67076-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67076-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02465.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67076
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|dominiq at lps dot ens.fr |
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
It seems to have been fixed by revision r231649.
>From gcc-bugs-return-602342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 13:01:32 2018
Return-Path: <gcc-bugs-return-602342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119862 invoked by alias); 21 Apr 2018 13:01: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 119822 invoked by uid 48); 21 Apr 2018 13:01:28 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85491] New: [8 Regression] scimark LU Decomposition test 15% slower than GCC 7, 30% slower than peak
Date: Sat, 21 Apr 2018 13:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85491-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02466.txt.bz2
Content-length: 864
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85491
Bug ID: 85491
Summary: [8 Regression] scimark LU Decomposition test 15%
slower than GCC 7, 30% slower than peak
Product: gcc
Version: 8.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
https://gcc.opensuse.org/gcc-old/c++bench-czerny/nbench/ shows a LU
decomposition
slowdown between r257710 and r257760 after a previous improvement between
r253986 and r254023.
These are numbers on Haswell with -O3 -ffast-math -funroll-loops -march=native.
The improvement is likely r253993/r254012, x86 vectorization cost changes. The
regression might be r257734.
>From gcc-bugs-return-602343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 13:02:28 2018
Return-Path: <gcc-bugs-return-602343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121255 invoked by alias); 21 Apr 2018 13:02: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 121174 invoked by uid 48); 21 Apr 2018 13:02:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85491] [8 Regression] scimark LU Decomposition test 15% slower than GCC 7, 30% slower than peak
Date: Sat, 21 Apr 2018 13:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: missed-optimization, needs-bisection
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.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget blocked target_milestone
Message-ID: <bug-85491-4-JVsSuAqkCV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85491-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85491-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02467.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85491
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization,
| |needs-bisection
Target| |x86_64-*-*
Blocks| |79703, 53947
Target Milestone|--- |8.0
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79703
[Bug 79703] [meta-bug] SciMark 2.0 performance issues
>From gcc-bugs-return-602344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 13:19:03 2018
Return-Path: <gcc-bugs-return-602344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41670 invoked by alias); 21 Apr 2018 13:19: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 41558 invoked by uid 48); 21 Apr 2018 13:18:59 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65892] gcc fails to implement N685 aliasing of union members
Date: Sat, 21 Apr 2018 13:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: alias
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: SUSPENDED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65892-4-uYpKlBpuq8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65892-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65892-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02468.txt.bz2
Content-length: 2155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65892
--- Comment #36 from David Brown <david at westcontrol dot com> ---
(In reply to Martin Sebor from comment #34)
> I think in the use case below:
>
> struct { int i; char buf[4]; } s, r;
> *(float *)s.buf = 1.;
> r = s;
>
> the aggregate copy has to be viewed as a recursive copy of each of its
> members and copying buf[4] must be viewed as a memcpy, Char is definitely
> special (it can accesses anything with impunity, even indeterminate values).
> That said, I don't think the rules allow char arrays to be treated as
> allocated storage so while the store to s.buf via float* may be valid it
> doesn't change the effective type of s.buf and so the only way to read the
> float value stored in it is to copy it byte-by-byte (i.e., copy the float
> representation) to an object whose effective type is float. Some of the
> papers that deal with the effective type rules might touch on this (e.g., DR
> 236, Clark's N1520
In bare metal embedded development, it is common to have to have a way to treat
static declared storage (like a char[] array) as a pool for dynamic storage.
Often you don't want to use standard library malloc() because of requirements
on deterministic timing, etc. What you are saying here is that this is not
possible - meaning there is no way to write such malloc replacement in normal C
code. (It is possible, I think, to use gcc extensions such as the "may_alias"
type attribute and the "malloc" function attribute. And -fno-strict-alias is
always a safe resort.) It would be /very/ nice if there were a way to declare
statically allocated pools of memory that could be doled out by user-made
functions and - like malloc'ed memory - take their effective type when used.
It would be even better if there were a standard way to say that the initial
value of such memory is "unspecified". The compiler and linker could give such
memory a static allocation (essential for small embedded systems with limited
memory, so that you can be sure of your memory usage) but there would be no
need for zeroing the memory at startup.
>From gcc-bugs-return-602345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 13:38:29 2018
Return-Path: <gcc-bugs-return-602345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67073 invoked by alias); 21 Apr 2018 13:38: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 66985 invoked by uid 48); 21 Apr 2018 13:38:24 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65892] gcc fails to implement N685 aliasing of union members
Date: Sat, 21 Apr 2018 13:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: alias
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: SUSPENDED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65892-4-ov2d0T4czN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65892-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65892-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02469.txt.bz2
Content-length: 2379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65892
--- Comment #37 from David Brown <david at westcontrol dot com> ---
(In reply to Martin Sebor from comment #35)
> Here are the proposed changes:
>
> Pointer Provenance:
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2219.htm#proposed-technical-
> corrigendum
>
> Trap Representations:
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2220.htm#proposed-technical-
> corrigendum
>
> Unspecified Values:
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2221.htm#proposed-technical-
> corrigendum
I am a little unsure of the suggestions for unspecified values here. Can I
give some examples, to see if my interpretation is correct?
Let's use a new gcc builtin "__builtin_unspecified()" that returns an
unspecified value of int type, with no possible traps (no gcc target has trap
representations for int types, AFAIK).
int x = __builtin_unspecified();
int y = __builtin_unspecified();
if (x == y) doThis(); // The compiler can skip doThis()
if (x != y) doThat(); // The compiler can skip doThat() too
if (x == y) doThis(); else doThat();
// The compiler can choose to doThis() or doThat(),
// but must do one or the other
if (x == x) doThis(); // This compiler must doThis()
if (x != x) doThat(); // The compiler cannot doThat()
if (x == 3) doThis(); // The compiler can choose to doThis()
// if the compiler does choose to doThis() the it fixes the value of x as 3
if (x & 0x01) doThis(); else doThat();
// The compiler can choose do doThis() or doThat(),
// but that choice fixes the LSB of x
This could allow for a range of possible optimisations, especially if there is
a nice way to make unspecified values like __builtin_unspecified().
(Unspecified values of other types could be made by casts.) For example:
struct opt_int { bool valid; int value; };
struct opt_int safe_sqrt(struct opt_int x) {
opt_int y;
if (!x.valid || x.value < 0) {
y.valid = false;
y.value = __builtin_unspecified();
} else {
y.valid = true;
y.value = unsafe_sqrt(x.value);
}
return y;
}
This kind of structure would mean minimal effort when you only need part of a
struct to contain specified values.
>From gcc-bugs-return-602346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 13:51:45 2018
Return-Path: <gcc-bugs-return-602346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3381 invoked by alias); 21 Apr 2018 13:51: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 3331 invoked by uid 55); 21 Apr 2018 13:51:41 -0000
From: "zbeekman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68933] ICE when mixing "-fprofile-arcs -ftest-coverage" and "-fcoarray=lib" on gcc-6 only
Date: Sat, 21 Apr 2018 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zbeekman at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68933-4-UYZ6446kZT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02470.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68933
--- Comment #6 from Zaak <zbeekman at gmail dot com> ---
Thanks, I'll check it out.
On Sat, Apr 21, 2018 at 8:20 AM dominiq at lps dot ens.fr <
gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68933
>
> --- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> It seems to work with 7.3.0.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>From gcc-bugs-return-602347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 14:03:37 2018
Return-Path: <gcc-bugs-return-602347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29097 invoked by alias); 21 Apr 2018 14:03: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 28864 invoked by uid 48); 21 Apr 2018 14:03:33 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85220] [meta-bug, nvptx] Run trunk with og7 openacc testcases and analyze execution failures
Date: Sat, 21 Apr 2018 14: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85220-4-n2yQpyUaJC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85220-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85220-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02471.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85220
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> Marking resolved-fixed.
>From gcc-bugs-return-602348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 14:45:50 2018
Return-Path: <gcc-bugs-return-602348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124410 invoked by alias); 21 Apr 2018 14:45: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 124361 invoked by uid 48); 21 Apr 2018 14:45:45 -0000
From: "cantabile.desu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58372] internal compiler error: ix86_compute_frame_layout
Date: Sat, 21 Apr 2018 14:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cantabile.desu at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-58372-4-h3iEzGUXCt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58372-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58372-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02472.txt.bz2
Content-length: 1548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58372
Bitterblue <cantabile.desu at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cantabile.desu at gmail dot com
--- Comment #12 from Bitterblue <cantabile.desu at gmail dot com> ---
Hi.
This bug still exists in GCC 7.3.0. It comes up when cross-compiling Qt 5.10.1
from 64 bit Linux for 32 bit Windows.
Well, I assume it's the same bug because of comments seen online.
https://github.com/mxe/mxe/issues/2011
https://bugreports.qt.io/browse/QTBUG-64707
The offending function can be seen here:
https://github.com/qt/qtbase/blob/6c6ace9d23f90845fd424e474d38fe30f070775e/src/corelib/global/qrandom.cpp#L104
% i686-w64-mingw32-gcc -v
Using built-in specs.
COLLECT_GCC=i686-w64-mingw32-gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-w64-mingw32/7.3.0/lto-wrapper
Target: i686-w64-mingw32
Configured with: /build/mingw-w64-gcc/src/gcc/configure --prefix=/usr
--libexecdir=/usr/lib --target=i686-w64-mingw32
--enable-languages=c,lto,c++,objc,obj-c++,fortran,ada --enable-shared
--enable-static --enable-threads=posix --enable-fully-dynamic-string
--enable-libstdcxx-time=yes --with-system-zlib --enable-cloog-backend=isl
--enable-lto --disable-dw2-exceptions --enable-libgomp --disable-multilib
--enable-checking=release
Thread model: posix
gcc version 7.3.0 (GCC)
No problem with x86_64-w64-mingw32, of course.
>From gcc-bugs-return-602349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 17:41:31 2018
Return-Path: <gcc-bugs-return-602349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64052 invoked by alias); 21 Apr 2018 17:41: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 61833 invoked by uid 48); 21 Apr 2018 17:41:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85485] Remove -mcet
Date: Sat, 21 Apr 2018 17:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85485-4-q3hFWcKIhl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85485-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85485-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02473.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85485
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think it is better to keep it as alias, I think -mcet is much more familiar
to people than -mshstk.
>From gcc-bugs-return-602350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 18:41:16 2018
Return-Path: <gcc-bugs-return-602350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100013 invoked by alias); 21 Apr 2018 18:41:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99946 invoked by uid 48); 21 Apr 2018 18:41:12 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85485] Remove -mcet
Date: Sat, 21 Apr 2018 18:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85485-4-pFRziE6Ne1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85485-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85485-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02474.txt.bz2
Content-length: 873
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85485
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-04-21
Ever confirmed|0 |1
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #1)
> I think it is better to keep it as alias, I think -mcet is much more
> familiar to people than -mshstk.
-mcet won't get any shadow stack protection. -mcet/-mshstk are used to
enable SHSTK intrinsics to IMPLEMENT shadow stack, not to USE shadow stack.
To enable shadow stack protection, you need to use -fcf-protection=return.
-mcet will only lead user confusions.
>From gcc-bugs-return-602351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 19:56:26 2018
Return-Path: <gcc-bugs-return-602351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128349 invoked by alias); 21 Apr 2018 19:56:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128289 invoked by uid 48); 21 Apr 2018 19:56:21 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67076] [6/7/8 Regression] [F08] Critical inside a module procedure
Date: Sat, 21 Apr 2018 19:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-67076-4-yWJFE61sd7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67076-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67076-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02475.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67076
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Works on gcc-6, gcc-7 and gcc-8.
Closing as fixed.
>From gcc-bugs-return-602352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 21 21:38:37 2018
Return-Path: <gcc-bugs-return-602352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92279 invoked by alias); 21 Apr 2018 21:38: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 92171 invoked by uid 48); 21 Apr 2018 21:38:32 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/48696] Horrible bitfield code generation on x86
Date: Sat, 21 Apr 2018 21:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-48696-4-1rvsq7vx5F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02476.txt.bz2
Content-length: 186
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48696
--- Comment #17 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think some of this is due to SLOW_BYTE_ACCESS being set to 0.
>From gcc-bugs-return-602353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 01:23:42 2018
Return-Path: <gcc-bugs-return-602353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12440 invoked by alias); 22 Apr 2018 01:23:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12385 invoked by uid 48); 22 Apr 2018 01:23:37 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/71636] Missed optimization in variable alignment test
Date: Sun, 22 Apr 2018 01:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia 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: 7.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-71636-4-nK7SaQ7N0p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02477.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71636
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |7.0
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Fixed as mentioned.
>From gcc-bugs-return-602354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 03:37:09 2018
Return-Path: <gcc-bugs-return-602354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100340 invoked by alias); 22 Apr 2018 03:37: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 100276 invoked by uid 48); 22 Apr 2018 03:37:03 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52345] Missed optimization dealing with bools
Date: Sun, 22 Apr 2018 03:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-52345-4-IBFSnDgjgA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02478.txt.bz2
Content-length: 693
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52345
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The generic rule is:
original 3 expressions;
(((int)b) | i) == 0 -> (b == 0) & (i == 0) -> ~b & (i == 0)
(4 expressions; maybe 3 if b is a comparison and single use)
(((int)b) | i) != 0 -> (b != 0) | (i != 0) -> b | (i != 0)
(still 3 expressions)
(((int)b) & i) == 0 -> (b == 0) | ((i&1) == 0) -> ~b | ((i&1) == 0)
(4 expressions; maybe 3 if b is a comparison and single use)
(((int)b) & i) != 0 -> (b != 0) & ((i&1) != 0) -> b & ((i&1) != 0)
(still 3 expressions)
Where b is a "boolean" type variable.
>From gcc-bugs-return-602355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 03:56:39 2018
Return-Path: <gcc-bugs-return-602355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35660 invoked by alias); 22 Apr 2018 03:56: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 35618 invoked by uid 48); 22 Apr 2018 03:56:31 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/32648] missed-optimization: bit-manipulation via bool's
Date: Sun, 22 Apr 2018 03:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-32648-4-BpnqJJEuUb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02479.txt.bz2
Content-length: 415
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32648
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
For ARM64 we get:
f1:
ubfx x1, x0, 5, 1
ubfx x0, x0, 3, 1
eor w0, w1, w0
ret
f2:
eor w0, w0, w0, lsl 2
ubfx x0, x0, 5, 1
ret
Which might be just as the same really depending if the lsl is not split away
from the eor.
>From gcc-bugs-return-602356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 11:54:48 2018
Return-Path: <gcc-bugs-return-602356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63439 invoked by alias); 22 Apr 2018 11:54: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 63396 invoked by uid 48); 22 Apr 2018 11:54:43 -0000
From: "aurelien at aurel32 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85492] New: riscv64: endless when throwing an exception from a constructor
Date: Sun, 22 Apr 2018 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aurelien at aurel32 dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-85492-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02480.txt.bz2
Content-length: 898
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85492
Bug ID: 85492
Summary: riscv64: endless when throwing an exception from a
constructor
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: aurelien at aurel32 dot net
Target Milestone: ---
Created attachment 44002
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44002&action=edit
test case
The attached C++ code, extracted from googletest, tries to throw an exception
from a constructor. On riscv64, the processes goes into an endless loop using
100% of the CPU instead. This is reproducible even at -O0, with GCC 7.3.0 and
GCC 8 snapshot from 20180414, under both QEMU and real hardware (SiFive
Unleashed).
>From gcc-bugs-return-602357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 12:49:03 2018
Return-Path: <gcc-bugs-return-602357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17095 invoked by alias); 22 Apr 2018 12:49: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 17043 invoked by uid 48); 22 Apr 2018 12:48:58 -0000
From: "ihorelo at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/85493] New: decltype can use deleted constructor in template function
Date: Sun, 22 Apr 2018 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ihorelo at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85493-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02481.txt.bz2
Content-length: 865
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85493
Bug ID: 85493
Summary: decltype can use deleted constructor in template
function
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: ihorelo at mail dot ru
Target Milestone: ---
decltype can use deleted constructor in template function
struct no_def
{
no_def() = delete;
};
template<typename T>
void test()
{
decltype(no_def()) a{}; // error in Clang and MSVC, no error in GCC
a = a; // get rid of warning
}
int main()
{
test<int>();
}
Please check
https://stackoverflow.com/questions/49965849/decltype-with-deleted-constructor-is-possible-in-template-function
>From gcc-bugs-return-602358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 12:55:46 2018
Return-Path: <gcc-bugs-return-602358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49483 invoked by alias); 22 Apr 2018 12:55: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 49459 invoked by uid 48); 22 Apr 2018 12:55:42 -0000
From: "ihorelo at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/85493] decltype can use deleted constructor and deleted function in template function
Date: Sun, 22 Apr 2018 12:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ihorelo at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-85493-4-iPUp4TQDWf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85493-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85493-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02482.txt.bz2
Content-length: 1286
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85493
Ihor Rudynskyi <ihorelo at mail dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|decltype can use deleted |decltype can use deleted
|constructor in template |constructor and deleted
|function |function in template
| |function
--- Comment #1 from Ihor Rudynskyi <ihorelo at mail dot ru> ---
also doesn`t work with deleted template function
template<typename...>
int foo() = delete;
template<typename...>
void test()
{
decltype(foo<int>()) a{};
}
int main()
{
test<>();
}(In reply to Ihor Rudynskyi from comment #0)
> decltype can use deleted constructor in template function
>
> struct no_def
> {
> no_def() = delete;
> };
>
> template<typename T>
> void test()
> {
> decltype(no_def()) a{}; // error in Clang and MSVC, no error in GCC
> a = a; // get rid of warning
> }
>
> int main()
> {
> test<int>();
> }
>
>
> Please check
> https://stackoverflow.com/questions/49965849/decltype-with-deleted-
> constructor-is-possible-in-template-function
>From gcc-bugs-return-602359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 13:40:33 2018
Return-Path: <gcc-bugs-return-602359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16084 invoked by alias); 22 Apr 2018 13:40: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 16048 invoked by uid 48); 22 Apr 2018 13:40:29 -0000
From: "ookawa_mi at yahoo dot co.jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85494] New: implementation of random_device on mingw is useless
Date: Sun, 22 Apr 2018 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ookawa_mi at yahoo dot co.jp
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-85494-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02483.txt.bz2
Content-length: 664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85494
Bug ID: 85494
Summary: implementation of random_device on mingw is useless
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: ookawa_mi at yahoo dot co.jp
Target Milestone: ---
In mingw environment, std::random_device uses mt19937 with fixed seed.
As the main purpose of random_device is seed of mt19937, it is inappropriate.
Please replace to REAL random number generator by rand_s or CryptoAPI.
>From gcc-bugs-return-602360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 13:50:41 2018
Return-Path: <gcc-bugs-return-602360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34028 invoked by alias); 22 Apr 2018 13:50: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 33975 invoked by uid 48); 22 Apr 2018 13:50:37 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85485] Remove -mcet
Date: Sun, 22 Apr 2018 13: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-85485-4-oXp5tUx70O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85485-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85485-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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-04/txt/msg02484.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85485
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.0
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
A set of patches is posted at
https://gcc.gnu.org/ml/gcc-patches/2018-04/msg01033.html
>From gcc-bugs-return-602361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Apr 22 14:16:06 2018
Return-Path: <gcc-bugs-return-602361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120043 invoked by alias); 22 Apr 2018 14:16: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 99948 invoked by uid 89); 22 Apr 2018 14:15:34 -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,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_SORBS_DUL,SPF_HELO_FAIL,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=Hx-languages-length:195, Proposal, investment, costa
X-HELO: DaCostaGroup.com
Received: from owx125.internetdsl.tpnet.pl (HELO DaCostaGroup.com) (46.170.179.125) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 22 Apr 2018 14:15:20 +0000
Reply-To: gdacosta100194@gmail.com
From: Gabriel da Costa <gabriel@DaCostaGroup.com>
To: gcc-bugs@gcc.gnu.org
Subject: Investment Project Proposal...
Date: Sun, 22 Apr 2018 14:16:00 -0000
Message-ID: <20180422161505.9EFD63C1A4B8D153@DaCostaGroup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2018-04/txt/msg02485.txt.bz2
Content-length: 170
Greetings. I am Gabriel Arcanjo da Costa of Sao Tome & Principe,
I am contacting you to undertake an investment project with me.
Contact me back for more details.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-04-21 10:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-85381-4@http.gcc.gnu.org/bugzilla/>
2018-04-21 10:10 ` [Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128 vries at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).