public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
[not found] <bug-85698-4@http.gcc.gnu.org/bugzilla/>
@ 2018-05-11 11:19 ` rguenth at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: rguenth at gcc dot gnu.org @ 2018-05-11 11:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I can see what the patch does to this testcase on x86_64 - it enables BB
vectorization of the first two loops after runrolling. I don't see anything
suspicious here on x86_64 and 525.x264_r works fine for me.
Can you claify whether test, ref or train inputs fail for you? I tried
AVX256, AVX128 and plain old SSE sofar without any issue but ref takes some
time...
Can you check whether the following reduced file produces the same assembly
for add4x4_idct as in the complete benchmark? If so it should be possible to
generate a runtime testcase from it. Please attach preprocessed source if
that doesn't work out.
Sofar I do suspect we are hitting a latent target issue?
#include <stdint.h>
static uint8_t x264_clip_uint8( int x )
{
return x&(~255) ? (-x)>>31 : x;
}
void add4x4_idct( uint8_t *p_dst, int16_t dct[16])
{
int16_t d[16];
int16_t tmp[16];
for( int i = 0; i < 4; i++ )
{
int s02 = dct[0*4+i] + dct[2*4+i];
int d02 = dct[0*4+i] - dct[2*4+i];
int s13 = dct[1*4+i] + (dct[3*4+i]>>1);
int d13 = (dct[1*4+i]>>1) - dct[3*4+i];
tmp[i*4+0] = s02 + s13;
tmp[i*4+1] = d02 + d13;
tmp[i*4+2] = d02 - d13;
tmp[i*4+3] = s02 - s13;
}
for( int i = 0; i < 4; i++ )
{
int s02 = tmp[0*4+i] + tmp[2*4+i];
int d02 = tmp[0*4+i] - tmp[2*4+i];
int s13 = tmp[1*4+i] + (tmp[3*4+i]>>1);
int d13 = (tmp[1*4+i]>>1) - tmp[3*4+i];
d[0*4+i] = ( s02 + s13 + 32 ) >> 6;
d[1*4+i] = ( d02 + d13 + 32 ) >> 6;
d[2*4+i] = ( d02 - d13 + 32 ) >> 6;
d[3*4+i] = ( s02 - s13 + 32 ) >> 6;
}
for( int y = 0; y < 4; y++ )
{
for( int x = 0; x < 4; x++ )
p_dst[x] = x264_clip_uint8( p_dst[x] + d[y*4+x] );
p_dst += 32;
}
}
>From gcc-bugs-return-604424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 12:25:36 2018
Return-Path: <gcc-bugs-return-604424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59420 invoked by alias); 11 May 2018 12:25: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 50371 invoked by uid 48); 11 May 2018 12:25:28 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] suboptimal code without constexpr
Date: Fri, 11 May 2018 12:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antoshkka 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-85747-4-ZZO1G92Cku@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01319.txt.bz2
Content-length: 725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
--- Comment #3 from Antony Polukhin <antoshkka at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> What's the reason for writing the code as you pasted it?
I've tried to provide a simplified case. In real world `generate()` function
will have some arguments and depending on those it could be either constexpr
evaluated or not.
There's plenty of pre C++14 code that is not well maintained and does not use
constexpr a lot, but functions could be treated and evaluated as constexpr in
C++14.
Main reason for this ticket - is to have some out-of-the-box speedup for such
legacy code. Function without arguments seemed to be a good place to start.
>From gcc-bugs-return-604425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 12:28:47 2018
Return-Path: <gcc-bugs-return-604425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66739 invoked by alias); 11 May 2018 12:28: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 66613 invoked by uid 48); 11 May 2018 12:28:42 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] suboptimal code without constexpr
Date: Fri, 11 May 2018 12:28: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antoshkka 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-85747-4-4TN2HX5lke@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01320.txt.bz2
Content-length: 972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
--- Comment #4 from Antony Polukhin <antoshkka at gmail dot com> ---
(In reply to Marc Glisse from comment #2)
> (In reply to Antony Polukhin from comment #0)
> > Could the compiler detect that `a[7]` holds values known at compile time and
> > force the constexpr on `sort(a + 0, a + 7);`?
>
> There has to be a limit. If I write a program that computes the trillion's
> decimal of pi, this is a constant, do you expect the compiler to evaluate
> the whole program and compile it to just return cst? We are moving into a
> realm where we would want to mix compilation and execution, sort of JIT.
> For smaller functions, some heuristics could be used to try compile-time
> evaluation, but sorting an array of size 7 already seems large to me.
Does providing some kind of -Oon-the-fly switch solves the issue with JIT
compile times while still allows more optimizations for the traditional non JIT
-O2 builds?
>From gcc-bugs-return-604426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 12:42:10 2018
Return-Path: <gcc-bugs-return-604426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117634 invoked by alias); 11 May 2018 12:42: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 114882 invoked by uid 48); 11 May 2018 12:42:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85717] anonymous union in initializer list : do not handle the types correctly
Date: Fri, 11 May 2018 12:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85717-4-Ea6MCH21Bw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01321.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85717
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This behaviour is required by the C++ standard, GCC is not allowed to change
it.
In C++20 you will be able to use designated-initializers to select which me,ber
of the union to initialize:
t1 = { 1 ,"a", { .real=3.4 } } ;
t1 = { 1 ,"a", { .integer = 2 } } ;
>From gcc-bugs-return-604427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:10:35 2018
Return-Path: <gcc-bugs-return-604427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70996 invoked by alias); 11 May 2018 13:10:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66834 invoked by uid 48); 11 May 2018 13:10:28 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] [8,9 regression] ARM -mbe8 behaviour doesn't match documentation
Date: Fri, 11 May 2018 13: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-85733-4-Nn8wTzoNUt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01322.txt.bz2
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|documentation |
--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Documentation is correct. That the implementation does not match it is the
problem.
>From gcc-bugs-return-604428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:26:56 2018
Return-Path: <gcc-bugs-return-604428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75511 invoked by alias); 11 May 2018 13:26: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 75401 invoked by uid 48); 11 May 2018 13:26:51 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] suboptimal code without constexpr
Date: Fri, 11 May 2018 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85747-4-J9ZxvFoTKi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01323.txt.bz2
Content-length: 779
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Antony Polukhin from comment #4)
> Does providing some kind of -Oon-the-fly switch solves the issue with JIT
> compile times while still allows more optimizations for the traditional non
> JIT -O2 builds?
Not sure what you mean by -Oon-the-fly. If you want to JIT compile the code,
you more or less need to embed a compiler in the executable...
The closest I can think of is -fprofile-values. It is possible to collect the
values of constants during a training run and use them during a second
compilation. But then knowing more constants in one compilation than the other
may change the code in ways that the PGO framework will not like.
>From gcc-bugs-return-604431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:31:49 2018
Return-Path: <gcc-bugs-return-604431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92787 invoked by alias); 11 May 2018 13:31: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 92629 invoked by uid 55); 11 May 2018 13:31:38 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] [8,9 regression] ARM -mbe8 behaviour doesn't match documentation
Date: Fri, 11 May 2018 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85733-4-HZZBi0udWP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01326.txt.bz2
Content-length: 1123
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Fri May 11 13:30:55 2018
New Revision: 260163
URL: https://gcc.gnu.org/viewcvs?rev=260163&root=gcc&view=rev
Log:
[arm] PR target/85733 Restore be8 linking behaviour for ARMv6-M and products
deriving from its capabilities
My patch last year to automate passing the be8 flag to the linker had
a nasty flaw in that I forgot entirely that the ARMv6-M architecture
did not derive its capabilities directly from the ARMv6 capability
list, but was a new group of capabilities (since it needs to leave out
the ARM -- notm -- feature bit). The feature list defined was thus
missing the be8 bit. Furthermore, any product derived from that
feature group consequently lacked the be8 feature as well and this
included all ARMv7 and ARMv8 parts.
The fix is embarrassingly simple...
PR target/85733
* config/arm/arm-cpus.in (fgroup ARMv6m): Add be8 feature.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/arm/arm-cpus.in
>From gcc-bugs-return-604429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:31:01 2018
Return-Path: <gcc-bugs-return-604429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90823 invoked by alias); 11 May 2018 13:31: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 90271 invoked by uid 55); 11 May 2018 13:30:22 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] [8,9 regression] ARM -mbe8 behaviour doesn't match documentation
Date: Fri, 11 May 2018 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85733-4-N7f301q4bc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01324.txt.bz2
Content-length: 1091
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Fri May 11 13:29:41 2018
New Revision: 260162
URL: https://gcc.gnu.org/viewcvs?rev=260162&root=gcc&view=rev
Log:
[arm] PR target/85733 Restore be8 linking behaviour for ARMv6-M and products
deriving from its capabilities
My patch last year to automate passing the be8 flag to the linker had
a nasty flaw in that I forgot entirely that the ARMv6-M architecture
did not derive its capabilities directly from the ARMv6 capability
list, but was a new group of capabilities (since it needs to leave out
the ARM -- notm -- feature bit). The feature list defined was thus
missing the be8 bit. Furthermore, any product derived from that
feature group consequently lacked the be8 feature as well and this
included all ARMv7 and ARMv8 parts.
The fix is embarrassingly simple...
PR target/85733
* config/arm/arm-cpus.in (fgroup ARMv6m): Add be8 feature.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/arm/arm-cpus.in
>From gcc-bugs-return-604430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:31:04 2018
Return-Path: <gcc-bugs-return-604430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90849 invoked by alias); 11 May 2018 13:31: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 90642 invoked by uid 48); 11 May 2018 13:30:52 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85734] --suggest-attribute=malloc misdiagnoses static functions
Date: Fri, 11 May 2018 13:31: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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-85734-4-2cjR4sWDUm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01325.txt.bz2
Content-length: 281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
There is function_always_visible_to_compiler_p which should disable this sort
of warning. So I suppose we want to test it prior warning about malloc
attribute?
>From gcc-bugs-return-604432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:41:46 2018
Return-Path: <gcc-bugs-return-604432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101998 invoked by alias); 11 May 2018 13:41: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 101916 invoked by uid 48); 11 May 2018 13:41:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85656] gcc.dg/ipa/ipa-icf-38.c FAILs
Date: Fri, 11 May 2018 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85656-4-PQ9ewQvB6v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01327.txt.bz2
Content-length: 1176
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Rainer Orth from comment #3)
> Created attachment 44108 [details]
> i386-pc-solaris2.11 ipa-icf-38.exe.wpa.073i.icf
>
> It's only one part that fails
>
> FAIL: gcc.dg/ipa/ipa-icf-38.c scan-ltrans-tree-dump-not fixup_cfg4 "Function
> bar"
>
> which was introduced by
>
> 2018-05-02 Tom de Vries <tom@codesourcery.com>
>
> PR testsuite/85106
> * gcc.dg/ipa/ipa-icf-38.c: Use scan-ltrans-tree-dump.
> [...]
According to log file alias support is mission on solaris. Thus following patch
should fix that by skipping the test:
diff --git a/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
b/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
index 85531ab1cf3..45525844551 100644
--- a/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
+++ b/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
@@ -1,4 +1,5 @@
/* { dg-do link } */
+/* { dg-require-alias "" } */
/* { dg-options "-O2 -fdump-ipa-icf -flto -fdump-tree-fixup_cfg4" } */
/* { dg-require-effective-target lto } */
/* { dg-additional-sources "ipa-icf-38a.c" }*/
Can you please verify that?
>From gcc-bugs-return-604433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:42:40 2018
Return-Path: <gcc-bugs-return-604433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105720 invoked by alias); 11 May 2018 13:42: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 105626 invoked by uid 48); 11 May 2018 13:42:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85656] gcc.dg/ipa/ipa-icf-38.c FAILs
Date: Fri, 11 May 2018 13:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_fail
Message-ID: <bug-85656-4-aRXbMJ7mnk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01328.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Known to fail| |9.0
>From gcc-bugs-return-604434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:46:01 2018
Return-Path: <gcc-bugs-return-604434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119042 invoked by alias); 11 May 2018 13:45:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118875 invoked by uid 48); 11 May 2018 13:45:50 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/48200] linking shared library with LTO results in different exported symbols
Date: Fri, 11 May 2018 13:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-48200-4-d8kog0U4fC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48200-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48200-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01329.txt.bz2
Content-length: 1101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #20 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Xi Ruoyao from comment #19)
> I think the best result would be like FMV, for e.g.
>
> int foo(void) __attribute__((symver("@1.1")))
> {
> return 0;
> }
>
> int foo(void) __attribute__((symver("@@1.2")))
> {
> return 1;
> }
>
> Would produce two symbols "foo.symver.1.1" and "foo.symver.1.2", and
>
> .symver foo.symver.1.1 foo@1.1
> .symver foo.symver.1.2 foo@@1.2
>
> And we can also use
>
> int foo(void) __attribute__((symver("@1.0"), alias("foo_old")));
>
> But this seems difficult in C FE, it tends to complain the "redefine" of foo
> - note that FMV is still only for C++ until now.
Sounds reasonable to me. I have some experience with MVC so I will work on that
in this stage1.
>From gcc-bugs-return-604435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:46:43 2018
Return-Path: <gcc-bugs-return-604435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128145 invoked by alias); 11 May 2018 13:46: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 126265 invoked by uid 48); 11 May 2018 13:46:38 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] [8,9 regression] ARM -mbe8 behaviour doesn't match documentation
Date: Fri, 11 May 2018 13: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85733-4-275mkpPmdo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01330.txt.bz2
Content-length: 434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Fixed
>From gcc-bugs-return-604436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:53:03 2018
Return-Path: <gcc-bugs-return-604436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30503 invoked by alias); 11 May 2018 13:53: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 27947 invoked by uid 48); 11 May 2018 13:52:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85725] strchr and strstr of a one-element array with a non-empty string can be assumed to return null
Date: Fri, 11 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: 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:
Message-ID: <bug-85725-4-1z4OVx26Sb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01331.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85725
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
That's right: unless otherwise specified, string functions require as arguments
valid strings, or as the C++ standard defines them, NTBS (nul-terminated byte
string). Thus the only valid string that can be stored in char[1] is the empty
string. The memchr function must be used to find the first occurrence of a
character in an arbitrary (not necesarily nul-terminated) sequence of bytes.
>From gcc-bugs-return-604437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 13:57:00 2018
Return-Path: <gcc-bugs-return-604437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48243 invoked by alias); 11 May 2018 13:57: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 48132 invoked by uid 48); 11 May 2018 13:56:56 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85734] --suggest-attribute=malloc misdiagnoses static functions
Date: Fri, 11 May 2018 13:57: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85734-4-guCWLKsXlf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01332.txt.bz2
Content-length: 415
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
prathamesh3492 at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |prathamesh3492 at gcc dot gnu.org
--- Comment #3 from prathamesh3492 at gcc dot gnu.org ---
I will take a look.
Regards,
Prathamesh
>From gcc-bugs-return-604438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 14:03:41 2018
Return-Path: <gcc-bugs-return-604438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85312 invoked by alias); 11 May 2018 14: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 85248 invoked by uid 48); 11 May 2018 14:03:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/81914] [7 Regression] gcc 7.1 generates branch for code which was branchless in earlier gcc version
Date: Fri, 11 May 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: middle-end
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-81914-4-Y3XPm6bAdL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81914-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81914-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01333.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81914
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #14 from Martin Liška <marxin at gcc dot gnu.org> ---
Jakub I see you fixed the most interesting case, can we close that?
>From gcc-bugs-return-604439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 14:47:02 2018
Return-Path: <gcc-bugs-return-604439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14684 invoked by alias); 11 May 2018 14:47: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 11770 invoked by uid 48); 11 May 2018 14:46:57 -0000
From: "thopre01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85434] Address of stack protector guard spilled to stack on ARM
Date: Fri, 11 May 2018 14:47: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thopre01 at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: thopre01 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85434-4-Ovtagi75GF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85434-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85434-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01334.txt.bz2
Content-length: 216
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85434
--- Comment #13 from Thomas Preud'homme <thopre01 at gcc dot gnu.org> ---
Remains now:
1) add support for PIC access to the guard
2) finish cleanup of the patch
>From gcc-bugs-return-604440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:20:47 2018
Return-Path: <gcc-bugs-return-604440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39678 invoked by alias); 11 May 2018 15:20: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 39600 invoked by uid 48); 11 May 2018 15:20:41 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/82571] missing strlen optimization for memchr
Date: Fri, 11 May 2018 15:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.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: cf_known_to_fail
Message-ID: <bug-82571-4-4X2Kgp2mUL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82571-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82571-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01335.txt.bz2
Content-length: 1305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82571
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |6.4.0, 7.3.0, 8.1.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Looks like I forgot to include a test case in comment #0. Here's a simple one
showing the optimization done for strchr and the missing equivalent
optimization for memchr.
$ cat t.c && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout t.c
int f0 (void)
{
char a[] = "123";
return 0 != __builtin_strchr (a, 0); // folded to 1
}
int f1 (void)
{
char a[] = "123";
return 0 != __builtin_memchr (a, 0, sizeof a); // not folded but could be
}
;; Function f0 (f0, funcdef_no=0, decl_uid=1956, cgraph_uid=0, symbol_order=0)
f0 ()
{
<bb 2> [local count: 1073741825]:
return 1;
}
;; Function f1 (f1, funcdef_no=1, decl_uid=1960, cgraph_uid=1, symbol_order=1)
f1 ()
{
char a[4];
void * _1;
_Bool _2;
int _5;
<bb 2> [local count: 1073741825]:
a = "123";
_1 = __builtin_memchr (&a, 0, 4);
_2 = _1 != 0B;
_5 = (int) _2;
a ={v} {CLOBBER};
return _5;
}
>From gcc-bugs-return-604441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:23:34 2018
Return-Path: <gcc-bugs-return-604441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42198 invoked by alias); 11 May 2018 15:23:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42120 invoked by uid 48); 11 May 2018 15:23:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] suboptimal code without constexpr
Date: Fri, 11 May 2018 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
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-85747-4-QZzAjqeeRX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01336.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
IMHO just use constexpr if you care about compile time evaluation guarantees,
that is what it has been added for.
>From gcc-bugs-return-604442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:25:37 2018
Return-Path: <gcc-bugs-return-604442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44699 invoked by alias); 11 May 2018 15:25:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44332 invoked by uid 48); 11 May 2018 15:25:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Fri, 11 May 2018 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85746-4-q71K7JDm0Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01337.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For different versions there is the
http://gcc.gnu.org/ml/gcc-patches/2018-03/msg00355.html
patch.
>From gcc-bugs-return-604443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:42:27 2018
Return-Path: <gcc-bugs-return-604443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71477 invoked by alias); 11 May 2018 15:42:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71457 invoked by uid 48); 11 May 2018 15:42:22 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84201] 549.fotonik3d_r from SPEC2017 fails verification with -mprefer-vector-width%6 or 512 on Zen
Date: Fri, 11 May 2018 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm 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-84201-4-15WENBlgQw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84201-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84201-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01338.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84201
--- Comment #1 from Martin Jambor <jamborm at gcc dot gnu.org> ---
When benchmarking GCC 8 on an older Ivy Bridge Xeon, I also got 549.fotonik3d_r
verification error just with -Ofast -g -march=native -mtune=native
>From gcc-bugs-return-604444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:49:11 2018
Return-Path: <gcc-bugs-return-604444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83908 invoked by alias); 11 May 2018 15:49: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 83823 invoked by uid 48); 11 May 2018 15:49:07 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Fri, 11 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: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85746-4-R0Lr2elIOq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01339.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> For different versions there is the
> http://gcc.gnu.org/ml/gcc-patches/2018-03/msg00355.html
> patch.
Time to ping that one? ;-)
(I don't have a particular opinion about how __builtin_early_constant_p should
behave)
>From gcc-bugs-return-604445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:55:53 2018
Return-Path: <gcc-bugs-return-604445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106189 invoked by alias); 11 May 2018 15:55: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 106090 invoked by uid 55); 11 May 2018 15:55:47 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85655] [8/9 Regression] ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault
Date: Fri, 11 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: ipa
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85655-4-nHpi9BvN6E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01340.txt.bz2
Content-length: 677
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Fri May 11 15:55:15 2018
New Revision: 260165
URL: https://gcc.gnu.org/viewcvs?rev=260165&root=gcc&view=rev
Log:
Check is_single_const in intersect_with_plats
2018-05-11 Martin Jambor <mjambor@suse.cz>
PR ipa/85655
* ipa-cp.c (intersect_with_plats): Check that the lattice contains
single const.
testsuite/
* g++.dg/lto/pr85655_0.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/lto/pr85655_0.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-cp.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:58:11 2018
Return-Path: <gcc-bugs-return-604446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119521 invoked by alias); 11 May 2018 15:58: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 116627 invoked by uid 48); 11 May 2018 15:58:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85745] variable with asm register assignment allocated in wrong reg
Date: Fri, 11 May 2018 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ra
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-85745-4-tLJRBWZM2D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01341.txt.bz2
Content-length: 1462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85745
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> ---
The reason this happens is that the register variable is marked const. Don't
do that. If it is const, the compiler optimizes it more aggressively - it will
happily fold uses of the variable to the constant ininitializer, so the inline
asm becomes "r" (110) instead of "r" (__r2) and thus it can use any register.
This is how C++ behaved for years and how C in GCC behaves since the folding
improvements.
--- gcc/c/c-fold.c 2018-05-10 19:39:13.750529734 +0200
+++ gcc/c/c-fold.c 2018-05-11 17:57:12.941957170 +0200
@@ -165,7 +165,10 @@ c_fully_fold_internal (tree expr, bool i
if (!IS_EXPR_CODE_CLASS (kind) || kind == tcc_statement)
{
/* Except for variables which we can optimize to its initializer. */
- if (VAR_P (expr) && !lval && (optimize || in_init))
+ if (VAR_P (expr)
+ && !lval
+ && (optimize || in_init)
+ && !DECL_HARD_REGISTER (expr))
{
if (in_init)
ret = decl_constant_value_1 (expr, true);
would be a workaround for this, but not really sure if we want to use it.
>From gcc-bugs-return-604447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 15:59:05 2018
Return-Path: <gcc-bugs-return-604447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124672 invoked by alias); 11 May 2018 15:59: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 124624 invoked by uid 55); 11 May 2018 15:59:00 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85655] [8/9 Regression] ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault
Date: Fri, 11 May 2018 15:59: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.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85655-4-mpuJSde3e2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01342.txt.bz2
Content-length: 741
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
--- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Fri May 11 15:58:29 2018
New Revision: 260166
URL: https://gcc.gnu.org/viewcvs?rev=260166&root=gcc&view=rev
Log:
Check is_single_const in intersect_with_plats
2018-05-11 Martin Jambor <mjambor@suse.cz>
PR ipa/85655
* ipa-cp.c (intersect_with_plats): Check that the lattice contains
single const.
testsuite/
* g++.dg/lto/pr85655_0.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/lto/pr85655_0.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/ipa-cp.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 16:14:13 2018
Return-Path: <gcc-bugs-return-604448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25630 invoked by alias); 11 May 2018 16:14:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25566 invoked by uid 48); 11 May 2018 16:14:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85739] [8/9 Regression] internal compiler error: in finish_member_declaration, at cp/semantics.c:3057
Date: Fri, 11 May 2018 16:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-85739-4-Pb8wBJI0XL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01343.txt.bz2
Content-length: 1746
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85739
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org
Target Milestone|--- |8.2
Summary|internal compiler error: in |[8/9 Regression] internal
|finish_member_declaration, |compiler error: in
|at cp/semantics.c:3057 |finish_member_declaration,
| |at cp/semantics.c:3057
Ever confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
You don't really need the include,
typedef __PTRDIFF_TYPE__ ptrdiff_t;
template <typename a, int a::*> class b {};
template <typename a, const int a::*> class B { using e = ptrdiff_t; };
template <typename a, int a::*i, const int a::*n>
bool operator!=(B<a, n>, b<a, i>);
class l;
template <typename a, int a::*i> class m {
public:
using o = B<l, i>;
using iterator = b<l, i>;
};
class l {
public:
int f;
};
template <typename g, int g::*h> class F {
public:
using j = m<l, h>;
using o = typename j::o;
using iterator = typename j::iterator;
o begin() const;
};
class p {
bool k() const;
F<l, &l::f>::iterator c;
F<l, &l::f> d;
};
bool p::k() const {
if (d.begin() != c)
return true;
return false;
}
reproduces it too.
Started with r254843.
>From gcc-bugs-return-604449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 16:23:11 2018
Return-Path: <gcc-bugs-return-604449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33599 invoked by alias); 11 May 2018 16:23:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33505 invoked by uid 48); 11 May 2018 16:23:07 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85643] attribute nonstring fails to squash -Wstringop-truncation warning at an offset
Date: Fri, 11 May 2018 16:23: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: keywords short_desc
Message-ID: <bug-85643-4-DOlHh8mDLm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01344.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Summary|attribute nonstring fails |attribute nonstring fails
|to squash |to squash
|-Wstringop-truncation |-Wstringop-truncation
|warning |warning at an offset
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00566.html
>From gcc-bugs-return-604450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 16:43:44 2018
Return-Path: <gcc-bugs-return-604450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19165 invoked by alias); 11 May 2018 16:43:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19126 invoked by uid 48); 11 May 2018 16:43:39 -0000
From: "chrisgiorgi at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/85722] testsuite failure in libffi
Date: Fri, 11 May 2018 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chrisgiorgi 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-85722-4-DHPNNOqkOT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01345.txt.bz2
Content-length: 719
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85722
--- Comment #9 from Chris Giorgi <chrisgiorgi at gmail dot com> ---
Created attachment 44118
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44118&action=edit
gcc-7.3.1-r1.ebuild
Funtoo gcc ebuild attached, enabling go triggers libffi test failures.
Repo, including patches applied at:
https://github.com/TemptorSent/overlay-dev-gcc-kit/tree/master/sys-devel/gcc
Versions extracted from ebuild:
GCC_ARCHIVE_VER="7.3.0"
GCC_SVN_REV="259984"
GMP_VER="6.1.2"
GMP_EXTRAVER=""
MPFR_VER="4.0.1"
MPC_VER="1.1.0"
CLOOG_VER="0.18.4"
ISL_VER="0.16.1"
GNAT32="gnat-gpl-2014-x86-linux-bin.tar.gz"
GNAT64="gnat-gpl-2017-x86_64-linux-bin.tar.gz"
>From gcc-bugs-return-604451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 17:07:09 2018
Return-Path: <gcc-bugs-return-604451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110606 invoked by alias); 11 May 2018 17:07: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 110544 invoked by uid 48); 11 May 2018 17:07:04 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85745] variable with asm register assignment allocated in wrong reg
Date: Fri, 11 May 2018 17:07: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: ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85745-4-7Lb4HXK4rF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01346.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85745
Bernd Edlinger <bernd.edlinger at hotmail dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Removing const fixes the build for me.
Thanks for investigating!
>From gcc-bugs-return-604452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 17:29:54 2018
Return-Path: <gcc-bugs-return-604452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21525 invoked by alias); 11 May 2018 17:29: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 21425 invoked by uid 55); 11 May 2018 17:29:47 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85687] ICE in gfc_sym_identifier, at fortran/trans-decl.c:351
Date: Fri, 11 May 2018 17: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85687-4-t0pN498NiF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01347.txt.bz2
Content-length: 801
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 17:29:14 2018
New Revision: 260169
URL: https://gcc.gnu.org/viewcvs?rev=260169&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
Backport from trunk
* check.c (gfc_check_rank): Check that the argument is a data object.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
Backport from trunk
* gfortran.dg/pr85687.f90: new test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr85687.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/check.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 17:31:45 2018
Return-Path: <gcc-bugs-return-604453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23803 invoked by alias); 11 May 2018 17:31: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 23694 invoked by uid 55); 11 May 2018 17:31:41 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85521] [8/9 Regression] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2049
Date: Fri, 11 May 2018 17:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85521-4-cTHSyNoO0v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01348.txt.bz2
Content-length: 985
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85521
--- Comment #7 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 17:30:57 2018
New Revision: 260170
URL: https://gcc.gnu.org/viewcvs?rev=260170&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
Backport from trunk
* array.c (gfc_resolve_character_array_constructor): Substrings
with upper bound smaller than lower bound are zero length strings.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
Backport from trunk
* gfortran.dg/pr85521_1.f90: New test.
* gfortran.dg/pr85521_2.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr85521_1.f90
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr85521_2.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/array.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 17:33:06 2018
Return-Path: <gcc-bugs-return-604454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28219 invoked by alias); 11 May 2018 17:33: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 27928 invoked by uid 55); 11 May 2018 17:33:00 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70870] Segmentation violation in gfc_assign_data_value
Date: Fri, 11 May 2018 17:33: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-70870-4-HlvMhDntCv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01349.txt.bz2
Content-length: 843
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70870
--- Comment #11 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 17:32:28 2018
New Revision: 260171
URL: https://gcc.gnu.org/viewcvs?rev=260171&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
Backport from trunk
* data.c (gfc_assign_data_value): Check that a data object does
not also have default initialization.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
Backport from trunk
* gfortran.dg/pr70870_1.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr70870_1.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/data.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 17:58:40 2018
Return-Path: <gcc-bugs-return-604455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110615 invoked by alias); 11 May 2018 17:58:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105361 invoked by uid 55); 11 May 2018 17:58:35 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85687] ICE in gfc_sym_identifier, at fortran/trans-decl.c:351
Date: Fri, 11 May 2018 17:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85687-4-mkXijszgvR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01350.txt.bz2
Content-length: 801
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 17:58:03 2018
New Revision: 260174
URL: https://gcc.gnu.org/viewcvs?rev=260174&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
Backport from trunk
* check.c (gfc_check_rank): Check that the argument is a data object.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
Backport from trunk
* gfortran.dg/pr85687.f90: new test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/pr85687.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/check.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 17:59:42 2018
Return-Path: <gcc-bugs-return-604456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30024 invoked by alias); 11 May 2018 17:59:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27097 invoked by uid 55); 11 May 2018 17:59:37 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85521] [8/9 Regression] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2049
Date: Fri, 11 May 2018 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85521-4-nljb9qcmDb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01351.txt.bz2
Content-length: 985
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85521
--- Comment #8 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 17:59:05 2018
New Revision: 260175
URL: https://gcc.gnu.org/viewcvs?rev=260175&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
Backport from trunk
* array.c (gfc_resolve_character_array_constructor): Substrings
with upper bound smaller than lower bound are zero length strings.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
Backport from trunk
* gfortran.dg/pr85521_1.f90: New test.
* gfortran.dg/pr85521_2.f90: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/pr85521_1.f90
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/pr85521_2.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/array.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:01:18 2018
Return-Path: <gcc-bugs-return-604457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42103 invoked by alias); 11 May 2018 18:01: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 42005 invoked by uid 55); 11 May 2018 18:01:14 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70870] Segmentation violation in gfc_assign_data_value
Date: Fri, 11 May 2018 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-70870-4-BxEYHomuQZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01352.txt.bz2
Content-length: 843
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70870
--- Comment #12 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 18:00:41 2018
New Revision: 260176
URL: https://gcc.gnu.org/viewcvs?rev=260176&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
Backport from trunk
* data.c (gfc_assign_data_value): Check that a data object does
not also have default initialization.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
Backport from trunk
* gfortran.dg/pr70870_1.f90: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/pr70870_1.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/data.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:06:28 2018
Return-Path: <gcc-bugs-return-604458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105667 invoked by alias); 11 May 2018 18:06: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 101642 invoked by uid 48); 11 May 2018 18:06:24 -0000
From: "martingalvan at sourceware dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85749] New: Possible -Wsign-conversion false negative with std::default_random_engine
Date: Fri, 11 May 2018 18:06: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: martingalvan at sourceware 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-85749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01353.txt.bz2
Content-length: 2729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85749
Bug ID: 85749
Summary: Possible -Wsign-conversion false negative with
std::default_random_engine
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: martingalvan at sourceware dot org
Target Milestone: ---
I have the following code:
#include <chrono>
#include <random>
int main()
{
const auto seed =
std::chrono::system_clock::now().time_since_epoch().count();
std::default_random_engine generator(seed);
generator.seed(seed);
return 0;
}
If I build this using g++ -std=c++17 -Wsign-conversion -o random random.cpp, I
get the following warning:
random.cpp: In function ‘int main()’:
random.cpp:9:24: warning: conversion to ‘std::linear_congruential_engine<long
unsigned int, 16807, 0, 2147483647>::result_type {aka long unsigned int}’ from
‘long int’ may change the sign of the result [-Wsign-conversion]
generator.seed(seed);
However, AFAIK the std::default_random_engine constructor also takes a
result_type (which should be unsigned). Therefore, the warning should also come
up when constructing 'generator'.
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.2.0-8ubuntu3.2' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)
>From gcc-bugs-return-604459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:07:27 2018
Return-Path: <gcc-bugs-return-604459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29406 invoked by alias); 11 May 2018 18:07:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26155 invoked by uid 48); 11 May 2018 18:07:23 -0000
From: "martingalvan at sourceware dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85749] Possible -Wsign-conversion false negative with std::default_random_engine
Date: Fri, 11 May 2018 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: martingalvan at sourceware dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-85749-4-lAiA2NbxdH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01354.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85749
--- Comment #1 from martingalvan at sourceware dot org ---
Created attachment 44119
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44119&action=edit
Preprocessed source
>From gcc-bugs-return-604460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:33:43 2018
Return-Path: <gcc-bugs-return-604460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57029 invoked by alias); 11 May 2018 18:33: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 56964 invoked by uid 55); 11 May 2018 18:33:37 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85687] ICE in gfc_sym_identifier, at fortran/trans-decl.c:351
Date: Fri, 11 May 2018 18:33: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: 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:
Message-ID: <bug-85687-4-DI5NlZGjhx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01355.txt.bz2
Content-length: 801
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
--- Comment #6 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 18:33:05 2018
New Revision: 260179
URL: https://gcc.gnu.org/viewcvs?rev=260179&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
Backport from trunk
* check.c (gfc_check_rank): Check that the argument is a data object.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
Backport from trunk
* gfortran.dg/pr85687.f90: new test.
Added:
branches/gcc-6-branch/gcc/testsuite/gfortran.dg/pr85687.f90
Modified:
branches/gcc-6-branch/gcc/fortran/ChangeLog
branches/gcc-6-branch/gcc/fortran/check.c
branches/gcc-6-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:34:50 2018
Return-Path: <gcc-bugs-return-604461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58733 invoked by alias); 11 May 2018 18:34:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58672 invoked by uid 55); 11 May 2018 18:34:45 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85521] [8/9 Regression] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2049
Date: Fri, 11 May 2018 18:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85521-4-wdEvOw8ekJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01356.txt.bz2
Content-length: 985
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85521
--- Comment #9 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 18:34:14 2018
New Revision: 260180
URL: https://gcc.gnu.org/viewcvs?rev=260180&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
Backport from trunk
* array.c (gfc_resolve_character_array_constructor): Substrings
with upper bound smaller than lower bound are zero length strings.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
Backport from trunk
* gfortran.dg/pr85521_1.f90: New test.
* gfortran.dg/pr85521_2.f90: New test.
Added:
branches/gcc-6-branch/gcc/testsuite/gfortran.dg/pr85521_1.f90
branches/gcc-6-branch/gcc/testsuite/gfortran.dg/pr85521_2.f90
Modified:
branches/gcc-6-branch/gcc/fortran/ChangeLog
branches/gcc-6-branch/gcc/fortran/array.c
branches/gcc-6-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:35:56 2018
Return-Path: <gcc-bugs-return-604462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67476 invoked by alias); 11 May 2018 18:35: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 67412 invoked by uid 55); 11 May 2018 18:35:52 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70870] Segmentation violation in gfc_assign_data_value
Date: Fri, 11 May 2018 18:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-70870-4-TVwCdneg5C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01357.txt.bz2
Content-length: 843
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70870
--- Comment #13 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 18:35:20 2018
New Revision: 260181
URL: https://gcc.gnu.org/viewcvs?rev=260181&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
Backport from trunk
* data.c (gfc_assign_data_value): Check that a data object does
not also have default initialization.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
Backport from trunk
* gfortran.dg/pr70870_1.f90: New test.
Added:
branches/gcc-6-branch/gcc/testsuite/gfortran.dg/pr70870_1.f90
Modified:
branches/gcc-6-branch/gcc/fortran/ChangeLog
branches/gcc-6-branch/gcc/fortran/data.c
branches/gcc-6-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:37:42 2018
Return-Path: <gcc-bugs-return-604465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70600 invoked by alias); 11 May 2018 18: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 70541 invoked by uid 48); 11 May 2018 18:37:38 -0000
From: "hpa at zytor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/84595] Add __builtin_break() built-in for a breakpointing mechanism
Date: Fri, 11 May 2018 18:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hpa at zytor dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84595-4-4Wn5VM9mmc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84595-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84595-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01360.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84595
H. Peter Anvin <hpa at zytor dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hpa at zytor dot com
--- Comment #9 from H. Peter Anvin <hpa at zytor dot com> ---
How is this different from raise(SIGTRAP);?
>From gcc-bugs-return-604464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:37:14 2018
Return-Path: <gcc-bugs-return-604464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69155 invoked by alias); 11 May 2018 18:37:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69069 invoked by uid 48); 11 May 2018 18:37:09 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33056] [Meta-bug] Data - statement related bugs
Date: Fri, 11 May 2018 18:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-33056-4-KCr2cf7eir@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-33056-4@http.gcc.gnu.org/bugzilla/>
References: <bug-33056-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01359.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33056
Bug 33056 depends on bug 70870, which changed state.
Bug 70870 Summary: Segmentation violation in gfc_assign_data_value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70870
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-604466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:37:51 2018
Return-Path: <gcc-bugs-return-604466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71322 invoked by alias); 11 May 2018 18:37: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 71257 invoked by uid 48); 11 May 2018 18:37:47 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85521] [8/9 Regression] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2049
Date: Fri, 11 May 2018 18:37: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.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-85521-4-KgJBCfQURq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01361.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85521
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|8.2 |6.5
--- Comment #10 from kargl at gcc dot gnu.org ---
Fixed.
>From gcc-bugs-return-604463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:37:13 2018
Return-Path: <gcc-bugs-return-604463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69147 invoked by alias); 11 May 2018 18:37:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69033 invoked by uid 48); 11 May 2018 18:37:09 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70870] Segmentation violation in gfc_assign_data_value
Date: Fri, 11 May 2018 18:37: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status resolution target_milestone
Message-ID: <bug-70870-4-l2EhUoLIeY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01358.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70870
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |6.5
--- Comment #14 from kargl at gcc dot gnu.org ---
Fixed.
>From gcc-bugs-return-604467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:38:17 2018
Return-Path: <gcc-bugs-return-604467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75279 invoked by alias); 11 May 2018 18:38: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 73352 invoked by uid 48); 11 May 2018 18:38:13 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85687] ICE in gfc_sym_identifier, at fortran/trans-decl.c:351
Date: Fri, 11 May 2018 18:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl 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 target_milestone
Message-ID: <bug-85687-4-y2K6Z3cgTd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01362.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |6.5
--- Comment #7 from kargl at gcc dot gnu.org ---
Fixed.
>From gcc-bugs-return-604468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:39:21 2018
Return-Path: <gcc-bugs-return-604468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76708 invoked by alias); 11 May 2018 18:39: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 76663 invoked by uid 48); 11 May 2018 18:39:16 -0000
From: "stephan.kramer at imperial dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85750] New: Default initialization of derived type array missing
Date: Fri, 11 May 2018 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stephan.kramer at imperial dot ac.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01363.txt.bz2
Content-length: 6386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85750
Bug ID: 85750
Summary: Default initialization of derived type array missing
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: stephan.kramer at imperial dot ac.uk
Target Milestone: ---
In The following program, the derived type array that is returned by make_list
does not have its components initialized.
module bar
implicit none
type ilist
integer :: count = 0
integer, dimension(:), pointer :: ptr => null()
end type ilist
contains
function make_list(i)
integer, intent(in) :: i
type(ilist), dimension(2) :: make_list
make_list(i)%count = 1
end function make_list
end module bar
program foo
use bar
implicit none
type(ilist), dimension(:), allocatable :: mylist
allocate(mylist(1:2))
mylist = make_list(1)
print *, mylist%count
mylist = make_list(2)
print *, mylist%count
end program foo
What I get:
$ gfortran test.f90
$ ./a.out
1 0
1 1
What I expect:
1 0
0 1
i.e. make_list should return an array for which all entries have a zero %count
component, except for the specified entry that's set to 1.
The program does work correctly if I leave out the %ptr from the ilist derived
type definition.
Latest gfortran I've tried is 8.1, but I see the same failure on 7.3, 7.2 and
6.2. The results are correct with gfortran 5.4
$ gfortran -v test.f90
Driving: gfortran -v test.f90 -l gfortran -l m -shared-libgcc
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.1.0-1'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --with-as=/usr/bin/x86_64-linux-gnu-as
--with-ld=/usr/bin/x86_64-linux-gnu-ld --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.1.0 (Debian 8.1.0-1)
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
/usr/lib/gcc/x86_64-linux-gnu/8/f951 test.f90 -quiet -dumpbase test.f90
-mtune=generic -march=x86-64 -auxbase test -version -fintrinsic-modules-path
/usr/lib/gcc/x86_64-linux-gnu/8/finclude -o /tmp/cch78iQf.s
GNU Fortran (Debian 8.1.0-1) version 8.1.0 (x86_64-linux-gnu)
compiled by GNU C version 8.1.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran2008 (Debian 8.1.0-1) version 8.1.0 (x86_64-linux-gnu)
compiled by GNU C version 8.1.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
/usr/bin/x86_64-linux-gnu-as -v --64 -o /tmp/ccwUDNGB.o /tmp/cch78iQf.s
GNU assembler version 2.30 (x86_64-linux-gnu) using BFD version (GNU Binutils
for Debian) 2.30
Reading specs from /usr/lib/gcc/x86_64-linux-gnu/8/libgfortran.spec
rename spec lib to liborig
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/
LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/8/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
/usr/lib/gcc/x86_64-linux-gnu/8/collect2 -plugin
/usr/lib/gcc/x86_64-linux-gnu/8/liblto_plugin.so
-plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
-plugin-opt=-fresolution=/tmp/cczgT9xX.res -plugin-opt=-pass-through=-lgcc_s
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lquadmath
-plugin-opt=-pass-through=-lm -plugin-opt=-pass-through=-lgcc_s
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --sysroot=/
--build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu -dynamic-linker
/lib64/ld-linux-x86-64.so.2 -pie
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/Scrt1.o
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crti.o
/usr/lib/gcc/x86_64-linux-gnu/8/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/8
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib -L/lib/x86_64-linux-gnu
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../.. /tmp/ccwUDNGB.o -lgfortran -lm
-lgcc_s -lgcc -lquadmath -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
/usr/lib/gcc/x86_64-linux-gnu/8/crtendS.o
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crtn.o
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
>From gcc-bugs-return-604469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:52:24 2018
Return-Path: <gcc-bugs-return-604469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89159 invoked by alias); 11 May 2018 18:52: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 89109 invoked by uid 48); 11 May 2018 18:52:19 -0000
From: "hpa at zytor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85751] New: RFE: option to align code using breakpoint instructions when unreachable
Date: Fri, 11 May 2018 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hpa at zytor 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-85751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01364.txt.bz2
Content-length: 1049
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85751
Bug ID: 85751
Summary: RFE: option to align code using breakpoint
instructions when unreachable
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hpa at zytor dot com
Target Milestone: ---
For most (all?) targets, there exists a breakpoint or other trap instruction
which can be inserted at any point in the code stream, e.g. 0xcc (int3) on x86.
Currently, gcc aligns code by the default platform option, which is some kind
of NOP, as the assembler can't know if a fallthrough is possible.
It would be preferable to pad with a trapping instruction *if* the padding area
is unreachable and not subject to fallthrough.
This does not require any binutils changes, as the align directives already
optionally support specifying the value of the padding bytes.
>From gcc-bugs-return-604470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 18:58:58 2018
Return-Path: <gcc-bugs-return-604470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100351 invoked by alias); 11 May 2018 18:58: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 100203 invoked by uid 55); 11 May 2018 18:58:53 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85542] [6/7/8/9 Regression] ICE in check_inquiry, at fortran/expr.c:2426
Date: Fri, 11 May 2018 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85542-4-a3LLAEP0NP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85542-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85542-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01365.txt.bz2
Content-length: 666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85542
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri May 11 18:58:21 2018
New Revision: 260182
URL: https://gcc.gnu.org/viewcvs?rev=260182&root=gcc&view=rev
Log:
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85542
* expr.c (check_inquiry): Avoid NULL pointer dereference.
2018-05-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85542
* gfortran.dg/pr85542.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr85542.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/expr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 19:05:52 2018
Return-Path: <gcc-bugs-return-604471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17039 invoked by alias); 11 May 2018 19:05: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 16931 invoked by uid 48); 11 May 2018 19:05:46 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type
Date: Fri, 11 May 2018 19:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: alias, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82899-4-Z8OviNRLXj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01366.txt.bz2
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
--- Comment #16 from Marc Glisse <glisse at gcc dot gnu.org> ---
(patch should use 'fn && DECL_CONSTRUCTOR_P (fn)' since fn can be NULL)
As I was half expecting, messing with the types that directly doesn't work. It
means 'this' has type T*restrict, and if I try for instance to bind it with a
T*const& reference, gcc is unwilling to discard the restrict qualifier.
I wonder if modifying the declarations later (say during gimplification) to
mark them with restrict would work.
I'd rather avoid teaching the middle-end a second way that parameters can be
__restrict (being the first argument of a C++ constructor), better if this can
all be done in the front-end.
>From gcc-bugs-return-604472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 19:11:50 2018
Return-Path: <gcc-bugs-return-604472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74480 invoked by alias); 11 May 2018 19:11: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 74384 invoked by uid 48); 11 May 2018 19:11:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85749] Possible -Wsign-conversion false negative with std::default_random_engine
Date: Fri, 11 May 2018 19: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: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-85749-4-7PBODT4v5i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01367.txt.bz2
Content-length: 1371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85749
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
Component|c++ |libstdc++
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
There's also a template constructor, which is the one that gets used:
template<typename _Sseq, typename = typename
std::enable_if<!std::is_same<_Sseq, linear_congruential_engine>::value>
::type>
explicit
linear_congruential_engine(_Sseq& __q)
{ seed(__q); }
The conversion to unsigned now happens when calling seed(__q), which is in the
std::lib code and so gets suppressed because it's in a system header (and using
-Wsystem-headers produces a lot of warnings from the std::lib code).
That constructor is only supposed to be used for seed sequence types, but
nothign in the standard actually ensures that, and so it gets used for your
example too. That might be a defect in the standard.
I'm going to re-assign this to libstdc++, so we can make that constructor less
greedy.
>From gcc-bugs-return-604473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 19:15:50 2018
Return-Path: <gcc-bugs-return-604473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86322 invoked by alias); 11 May 2018 19:15: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 86183 invoked by uid 48); 11 May 2018 19:15:39 -0000
From: "hpa at zytor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/85752] New: RFE: self-relative (prepickled) pointers
Date: Fri, 11 May 2018 19:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hpa at zytor 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-85752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01368.txt.bz2
Content-length: 2374
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85752
Bug ID: 85752
Summary: RFE: self-relative (prepickled) pointers
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: hpa at zytor dot com
Target Milestone: ---
If a pointer is optionally stored as a self-relative value rather than
absolute, it would enable the following use cases containing arbitrarily
complex data structures without needing any special "pickling":
- Shared memory segments
- Persistent memory
- Shared libraries (without expensive fixups)
An type attribute (or similar) would have to be attached to the pointer; a
pointer to such a pointer would be incompatible with a non-relative pointer.
These use cases have in common that they involve memory areas that have to work
correctly when mapped at different virtual addresses.
This could also, optionally, allow for 4-byte pointers on 64-bit architectures,
although this could definitely cause strange bugs if such a pointer was
writable and was written with a pointer outside the memory area -- but in the
cases listed above, such a pointer would be invalid anyway.
The cost of referencing such a pointer should be fairly minimal. On
architectures which support base+index addressing, such as x86, the overhead
might even be zero in many cases, as a sequence like:
# *rsi += rax;
movq (%rsi),%rdx # Load pointer
addq (%rdx),%rax
... can be transformed into ...
movq (%rsi),%rdx # Load relative pointer
addq (%rsi,%rdx),%rax
Of course, expressions that are indexed relative to the loaded pointers would
require an additional add/lea instruction.
With 4-byte relative pointers, the sequence would use movslq instead of movq:
movslq (%rsi),%rdx # Load and sign extend relative pointer
addq (%rsi,%rdx),%rax
Storing pointer values to memory would typically require an extra subtract
operation, of course.
I am filing this under "other" as I'm not sure where it needs to go. At least
in C++ I it can actually be done without compiler changes by doing casting
between pointers and ptrdiff_t and wrapping it in a template, but I'm not sure
if that would wreck alias analysis.
>From gcc-bugs-return-604474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 19:22:55 2018
Return-Path: <gcc-bugs-return-604474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44325 invoked by alias); 11 May 2018 19:22: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 44258 invoked by uid 48); 11 May 2018 19:22:50 -0000
From: "hpa at zytor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/85752] RFE: self-relative (prepickled) pointers
Date: Fri, 11 May 2018 19:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hpa at zytor 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-85752-4-02SGkBaWZr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01369.txt.bz2
Content-length: 232
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85752
--- Comment #1 from H. Peter Anvin <hpa at zytor dot com> ---
N.B.: this presumably needs some kind of special treatment of NULL, to prevent
NULL from being an absolute value.
>From gcc-bugs-return-604475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 19:49:35 2018
Return-Path: <gcc-bugs-return-604475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124989 invoked by alias); 11 May 2018 19:49:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124937 invoked by uid 48); 11 May 2018 19:49:19 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85753] New: missing -Wrestrict on memcpy into a member array
Date: Fri, 11 May 2018 19:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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-85753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01370.txt.bz2
Content-length: 1599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85753
Bug ID: 85753
Summary: missing -Wrestrict on memcpy into a member array
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: ---
GCC 8 diagnoses only the first of the two equivalently overlapping calls to
memcpy in the test case below but not the second. Both should be diagnosed.
$ cat u.c && gcc -O2 -S -Wall -fdump-tree-wrestrict=/dev/stdout u.c
char a[16];
struct { char a[16]; } x;
void f (int i, int j)
{
__builtin_memcpy (&a[i], &a[j], 9); // -Wrestrict (good)
__builtin_memcpy (&x.a[i], &x.a[j], 9); // missing -Wrestrict
}
;; Function f (f, funcdef_no=0, decl_uid=1961, cgraph_uid=0, symbol_order=2)
u.c: In function ‘f’:
u.c:7:3: warning: ‘__builtin_memcpy’ accessing 9 bytes at offsets [0, 16] and
[0, 16] overlaps between 2 and 9 bytes at offset [0, 7] [-Wrestrict]
__builtin_memcpy (&a[i], &a[j], 9); // -Wrestrict (good)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
f (int i, int j)
{
char * _1;
char * _2;
char * _3;
char * _4;
sizetype _10;
sizetype _11;
<bb 2> [local count: 1073741825]:
_10 = (sizetype) j_5(D);
_1 = &a + _10;
_11 = (sizetype) i_6(D);
_2 = &a + _11;
__builtin_memcpy (_2, _1, 9);
_3 = &x + _10;
_4 = &x + _11;
__builtin_memcpy (_4, _3, 9);
return;
}
>From gcc-bugs-return-604476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 21:04:56 2018
Return-Path: <gcc-bugs-return-604476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27651 invoked by alias); 11 May 2018 21:04: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 27539 invoked by uid 48); 11 May 2018 21:04:52 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
Date: Fri, 11 May 2018 21:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85698-4-3H0BafiQfl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01371.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #5 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
>
> Can you claify whether test, ref or train inputs fail for you? I tried
> AVX256, AVX128 and plain old SSE sofar without any issue but ref takes some
> time...
>
I see the error for ref and test inputs. The train input appears to pass, but
then the FDO optimized version fails with the ref input also.
I will keep looking at the other stuff you requested.
>From gcc-bugs-return-604477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 21:14:05 2018
Return-Path: <gcc-bugs-return-604477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55827 invoked by alias); 11 May 2018 21:14: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 55759 invoked by uid 48); 11 May 2018 21:13:59 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85754] New: missing -Wrestrict on memcpy with non-constant offsets less than size
Date: Fri, 11 May 2018 21:14: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-85754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01372.txt.bz2
Content-length: 1400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85754
Bug ID: 85754
Summary: missing -Wrestrict on memcpy with non-constant offsets
less than size
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: ---
When memcpy is used to copy sequences at offsets within the same array
-Wrestrict uses the full range of each of the offsets even when the offsets are
trivially related and. When the distance between the offsets is less than the
size of the copy the copy is guaranteed to overlap, yet -Wrestrict is not
issued. The checker could work harder and try to detect at least some of these
cases.
$ cat z.c && gcc -O2 -S -Wall -fdump-tree-vrp=/dev/stdout z.c
void f (char *p, int i)
{
__builtin_memcpy (p + i, p + i + 4, 32); // missing -Wrestrict
}
...
Value ranges after VRP:
_1: ~[2147483648, 18446744071562067967]
_2: ~[2147483652, 18446744071562067971]
...
f (char * p, int i)
{
sizetype _1;
sizetype _2;
char * _3;
char * _4;
<bb 2> [local count: 1073741825]:
_1 = (sizetype) i_5(D);
_2 = _1 + 4;
_3 = p_6(D) + _2;
_4 = p_6(D) + _1;
__builtin_memcpy (_4, _3, 32);
return;
}
>From gcc-bugs-return-604478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 21:20:47 2018
Return-Path: <gcc-bugs-return-604478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71036 invoked by alias); 11 May 2018 21:20: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 70951 invoked by uid 48); 11 May 2018 21:20:43 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type
Date: Fri, 11 May 2018 21:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: alias, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-82899-4-fAKtcDPPD7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01373.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #44112|0 |1
is obsolete| |
--- Comment #17 from Marc Glisse <glisse at gcc dot gnu.org> ---
Created attachment 44120
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44120&action=edit
Successful patch
Changing the type during gimplification seems to work, it passes the testsuite.
>From gcc-bugs-return-604479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 22:55:53 2018
Return-Path: <gcc-bugs-return-604479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60810 invoked by alias); 11 May 2018 22:55: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 60758 invoked by uid 48); 11 May 2018 22:55:49 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85749] Possible -Wsign-conversion false negative with std::default_random_engine
Date: Fri, 11 May 2018 22:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.2.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: bug_status assigned_to
Message-ID: <bug-85749-4-RFc5EPbnTN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01374.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85749
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
>From gcc-bugs-return-604480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 23:10:40 2018
Return-Path: <gcc-bugs-return-604480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4239 invoked by alias); 11 May 2018 23:10: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 124055 invoked by uid 48); 11 May 2018 23:10:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85753] missing -Wrestrict on memcpy into a member array
Date: Fri, 11 May 2018 23:10: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: 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 bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-85753-4-f14hl8bLYB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01375.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85753
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-11
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00576.html
>From gcc-bugs-return-604481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 23:19:29 2018
Return-Path: <gcc-bugs-return-604481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45822 invoked by alias); 11 May 2018 23:19: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 45669 invoked by uid 48); 11 May 2018 23:19:24 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85755] New: PowerPC Gcc's -mupdate produces inefficient code on power8/power9 machines
Date: Fri, 11 May 2018 23:19: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: meissner 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-85755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01376.txt.bz2
Content-length: 1499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85755
Bug ID: 85755
Summary: PowerPC Gcc's -mupdate produces inefficient code on
power8/power9 machines
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
If you compile the following code for -mcpu=power8 or -mcpu=power9, it wants to
generate a PRE_INC loop. However, the GPR movdi insn constraint uses the 'Y'
constraint for store, due to the LD/STD instructions being ds-form
instructions. Ds-form instructions cannot have the bottom 2 bits set in the
offset field. Because the register allocator does not have a GPR store that it
thinks can do a store with update, it does a direct move to the floating point
registers, and does a floating point store with update there.
We should probably allow store with update and load with update forms (or
disable DImode from generating the PRE_INC/PRE_DEC/PRE_MODIFY instructions):
Code:
void loop (long *q, long n)
{
long i;
for (i = 0; i < n; i++)
q[i] = i;
}
The code generated is:
loop:
.LFB0:
cmpdi 0,4,0
blelr 0
mtctr 4
addi 3,3,-8
li 9,0
.p2align 4,,15
.L3:
mtvsrd 0,9
addi 9,9,1
stfdu 0,8(3)
bdnz .L3
blr
>From gcc-bugs-return-604483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 12 00:21:57 2018
Return-Path: <gcc-bugs-return-604483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61762 invoked by alias); 12 May 2018 00:21: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 61718 invoked by uid 48); 12 May 2018 00:21:53 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85755] PowerPC Gcc's -mupdate produces inefficient code on power8/power9 machines
Date: Sat, 12 May 2018 00:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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-85755-4-1wreMEy34V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01378.txt.bz2
Content-length: 217
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85755
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
That is, that GCC 8 did not do pre-increment, but it did no silliness
with float registers.
>From gcc-bugs-return-604482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 12 00:21:01 2018
Return-Path: <gcc-bugs-return-604482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60375 invoked by alias); 12 May 2018 00:21: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 60311 invoked by uid 48); 12 May 2018 00:20:57 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85755] PowerPC Gcc's -mupdate produces inefficient code on power8/power9 machines
Date: Sat, 12 May 2018 00:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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-85755-4-oHfSVoLiGf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01377.txt.bz2
Content-length: 1748
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85755
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-12
Ever confirmed|0 |1
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Before RA it is all just fine:
insn_cost 4 for 14: [++r121:DI]=r122:DI
REG_INC r121:DI
insn_cost 4 for 15: r122:DI=r122:DI+0x1
insn_cost 0 for 30: {pc={(r129:DI!=0x1)?L16:pc};r129:DI=r129:DI-0x1;clobber
scratch;clobber scratch;}
REG_BR_PROB 955630228
IRA make a good choice:
Disposition:
3:r121 l0 3 0:r122 l0 9 4:r125 l0 3 2:r126 l0 4
5:r127 l0 68 1:r129 l0 66
and then LRA comes along:
Choosing alt 6 in insn 14: (0) ^m (1) d {*movdi_internal64}
Creating newreg=132 from oldreg=122, assigning class FLOAT_REGS to r132
14: [++r121:DI]=r132:DI
REG_INC r121:DI
Inserting insn reload before:
35: r132:DI=r122:DI
We want to have alt 0 instead (r -> YZ), which gives
0 Non input pseudo reload: reject++
alt=0,overall=7,losers=1,rld_nregs=0
but we get alt 6 (d -> ^m), which gives
alt=6,overall=6,losers=1,rld_nregs=1
Putting the disparagement on the correct operand, i.e. as ^d -> m gives
alt=6,overall=12,losers=1 -- refuse
and we should make that change; but yes we want an stdu, too. Should "Y"
allow that?
GCC 7 did this fine; GCC 8 of a month ago, too. What changed?
>From gcc-bugs-return-604484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 12 00:35:40 2018
Return-Path: <gcc-bugs-return-604484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85865 invoked by alias); 12 May 2018 00:35: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 85768 invoked by uid 48); 12 May 2018 00:35:36 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85755] PowerPC Gcc's -mupdate produces inefficient code on power8/power9 machines
Date: Sat, 12 May 2018 00:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85755-4-DnnKvh2r5l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01379.txt.bz2
Content-length: 238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85755
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Sigh, i forgot -mcpu=power8 on that last test.
GCC 7 was just fine, stdu, everything.
GCC 8 was bad already.
>From gcc-bugs-return-604485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 12 02:30:24 2018
Return-Path: <gcc-bugs-return-604485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78907 invoked by alias); 12 May 2018 02:30: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 78658 invoked by uid 48); 12 May 2018 02:30:05 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85756] New: wrong code at -Os on x86-64-linux-gnu in 32-bit mode
Date: Sat, 12 May 2018 02:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
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/msg01380.txt.bz2
Content-length: 1483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85756
Bug ID: 85756
Summary: wrong code at -Os on x86-64-linux-gnu in 32-bit mode
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: su at cs dot ucdavis.edu
Target Milestone: ---
$ gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/home/su/software/tmp/gcc/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 9.0.0 20180511 (experimental) [trunk revision 260178] (GCC)
$
$ gcctk -m32 -O0 small.c; ./a.out
$
$ gcctk -m32 -Os small.c
$ ./a.out
Segmentation fault (core dumped)
$
-------------------------------------
int printf (const char *, ...);
int a, c, *e, f, h = 10;
short b;
unsigned int p;
void fn1 ()
{
unsigned j = 1, m = 430523;
int k, n = 1, *l = &h;
L:
p = m;
m = -((~65535U | j) - n);
f = b << ~(n - 8);
n = (m || b) ^ f;
j = p;
if (p < m)
*l = k < 3;
if (!n)
l = &k;
if (c)
{
printf ("%d", a);
goto L;
}
if (!*l)
*e = 1;
}
int main ()
{
fn1 ();
return 0;
}
>From gcc-bugs-return-604486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 12 09:13:39 2018
Return-Path: <gcc-bugs-return-604486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8701 invoked by alias); 12 May 2018 09:13: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 4946 invoked by uid 89); 12 May 2018 09:13:36 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_50,GIT_PATCH_2,HTML_MESSAGE,KAM_NUMSUBJECT,LIKELY_SPAM_BODY,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=gaming, living, powered, luxury
X-HELO: smtp35.ymlpsvr.com
Received: from smtp35.ymlpsvr.com (HELO smtp35.ymlpsvr.com) (185.83.51.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 12 May 2018 09:13:31 +0000
Date: Sat, 12 May 2018 09:13:00 -0000
To: gcc-bugs@gcc.gnu.org
From: Oasis Living Magazine <newsletter@myoasisliving.com>
Subject: Your Weekly Breeze - May. 10 - May. 16
Message-ID: <5964367a05c9fb6f7cb7564ca29bae0f@smtp35.ymlpsvr.com>
X-YMLPcode: zgbq+995+30583
MIME-Version: 1.0
Content-Type: text/plain; charset = "utf-8"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2018-05/txt/msg01381.txt.bz2
Content-length: 3732
--------------------------------------------------------------------------------
This email newsletter was sent to you in graphical HTML format.
If you're seeing this version, your email program prefers plain text emails.
You can read the original version online:
https://ymlpsend3.com/z5Pw7t
--------------------------------------------------------------------------------
Having problems viewing Weekly Breeze Click here (
http://myoasisliving.com/weekly_breeze/weekly_breeze.php ).
TOP PICS
May 10 - May 16
-->
breeze@ myoasisliving.com for your chance to win aHanayen gift voucher
in Bawadi Mall worth Dh100. To win, simply email your complete name
and indicate Hanayenin the subject and you will qualify for a random
draw.
*If you win, you have 30 days to pick up your prize. If your prize is
not collected within 30 days of notification, it will be cancelled.
Participants who have won before are not eligible to win again within
90 days after winning
-->
Ramadan around the world
The holy month is an important time for Muslims everywhere. Oasis
Living looks at some different cultures and their own unique
traditions when observing the occasion >> (
http://myoasisliving.com/en/article/article_detail/article_id_enc/2227a0ee80dd97c2808feb441e97a1d1
)
Reaching for something higher
Fasting during Ramadan is more than just fulfilling religious
expectations, says acclaimed life coach Dr Sumaya Alnasser. There are
deep spiritual benefits of the practice too >> (
http://myoasisliving.com/en/article/article_detail/article_id_enc/211a4965b81d4a9a63a95a2fc694e533
)
A touch of magic
New gaming app allows fans to step into the world of Harry Potter >>
(
http://myoasisliving.com/en/news/news_detail/news_id_enc/333abcbf2b3187e12154b1401ef156b
)
Rags to riches
A group of Dubai women use their knitting and stitching skills to
help the hungry children of the world. Oasis Living met with the
founder Barbara Evans >> (
http://myoasisliving.com/en/article/article_detail/article_id_enc/111a4965b81d4a9a63a95a2fc694e533
)
Luxury looming large
The Infniti QX80 delivers the goods with the precision
andcraftsmanship of a fine watch – a really big watch >> (
http://myoasisliving.com/en/article/article_detail/article_id_enc/4334ff6e2068fe903742747b23325c1a
)
"OTHER HIGHLIGHTS THIS WEEK"
15 May onwards
Sports Night in Danat Al Ain Resort's McGettigan’s.
Iftar at Danat Al Ain Resort's Arabesque from 7pm onwards: Dh110++
per person on weekdays, Dh129++ per on weekends. The hotel will also
be serving suhoor in their Ramadan tent from 8.30pm onwards: Dh30++
per person on weekdays, Dh50++ per on weekends.
Al Rikab Restaurant in AESGC's Equestrian Club will be serving iftar
from 7 to 9pm and then suhoor until 1am: Dh90 per person, Dh45 for
children aged seven to 12. Live entertainment available daily along
with a raffle draw.
Iftar buffet at Olive Tree in Aloft Al Ain: Dh120 per person on
weekdays, Dh140 per on weekends.
Iftar buffet at Elements in Hili Rayhaan by Rotana for Dh119 from
Saturdays to Wednesdays, and Dh139 on Thursdays and Fridays. Suhoor
available for Dh59.
Email us at breeze@myoasisliving.com and tell us what you like about
our Weekly Breeze. Let us know which stories you like to read about,
or what else you would like to see included. We appreciate all reader
feedback!
Forward weekly breeze to your friend (
http://www.myoasisliving.com/weekly_breeze/email_version/forward_to_friend_form.php?newsletter_version=html_weekly_breeze_may_10_may_16_2018&your_email=gcc-bugs@gcc.gnu.org
)
_____________________________
Unsubscribe / Change Profile: https://ymlpsend3.com/ugmwhmbhgsgmsbqmgyybggubuhw
Powered by YourMailingListProvider
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-05-11 11:19 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-85698-4@http.gcc.gnu.org/bugzilla/>
2018-05-11 11:19 ` [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581 rguenth 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).