public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486
[not found] <bug-68491-4@http.gcc.gnu.org/bugzilla/>
@ 2017-05-02 20:37 ` uros at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: uros at gcc dot gnu.org @ 2017-05-02 20:37 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 30211 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68491
--- Comment #4 from uros at gcc dot gnu.org ---
Author: uros
Date: Tue May 2 20:36:26 2017
New Revision: 247523
URL: https://gcc.gnu.org/viewcvs?rev=247523&root=gcc&view=rev
Log:
Backport from mainline
2017-05-01 Uros Bizjak <ubizjak@gmail.com>
PR target/68491
* config/i386/cpuid.h (__get_cpuid): Always return 0 when
__get_cpuid_max returns 0.
(__get_cpuid_count): Ditto.
Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/config/i386/cpuid.h
>From gcc-bugs-return-562379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 20:42:27 2017
Return-Path: <gcc-bugs-return-562379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72471 invoked by alias); 2 May 2017 20: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 72402 invoked by uid 48); 2 May 2017 20:42:23 -0000
From: "jens.maurer at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80598] New: -Wunused triggers for functions used in uninstantiated templates
Date: Tue, 02 May 2017 20:42: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jens.maurer at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-80598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00229.txt.bz2
Content-length: 968
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80598
Bug ID: 80598
Summary: -Wunused triggers for functions used in uninstantiated
templates
Product: gcc
Version: 7.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jens.maurer at gmx dot net
Target Milestone: ---
The all-new gcc 7.1.0 now shows this disturbing warning; gcc 6.3.0 didn't. It
seems unhelpful to issue an "unused function" warning for a function actually
used from an uninstantiated template. This situation might happen a lot in
#included header files. (Adding an instantiation of "g" silences the warning.)
$ g++ -Wunused x.cc
x.cc:1:13: warning: ‘void f()’ defined but not used [-Wunused-function]
static void f()
{ }
template<class T>
int g(T x)
{
f();
return 0;
}
>From gcc-bugs-return-562380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 20:55:34 2017
Return-Path: <gcc-bugs-return-562380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34901 invoked by alias); 2 May 2017 20:55:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34704 invoked by uid 48); 2 May 2017 20:55:29 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/79349] unused std::string is not optimized away in presense of a call
Date: Tue, 02 May 2017 20: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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-79349-4-TEWUod6z8Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79349-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79349-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00230.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79349
--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
With the call to foo(), this is an issue of alias analysis. Gcc wrongly
believes that the string escapes (probably because we store a pointer to the
string inside the string itself, with the small string optimization), and thus
that foo() might modify the string, so it needs to check if the destructor
needs to run, whether foo returns normally or throws an exception.
>From gcc-bugs-return-562381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 20:59:22 2017
Return-Path: <gcc-bugs-return-562381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47497 invoked by alias); 2 May 2017 20:59:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47452 invoked by uid 48); 2 May 2017 20:59:18 -0000
From: "jens.maurer at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80599] New: -Wuseless-cast triggers for inherited constructor
Date: Tue, 02 May 2017 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jens.maurer at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-80599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00231.txt.bz2
Content-length: 1081
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80599
Bug ID: 80599
Summary: -Wuseless-cast triggers for inherited constructor
Product: gcc
Version: 7.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jens.maurer at gmx dot net
Target Milestone: ---
All-new gcc 7.1.0 delivers a -Wuseless-cast warning for inherited constructors
involving reference parameters that the user cannot do anything about. This
did not happen with gcc 6.3.0.
struct B {
B(const int&);
};
struct D : B {
using B::B;
};
D d2 = 0;
$ g++ -Wuseless-cast -c y.cc
y.cc: In constructor ‘D::D(const int&) [inherited from B]’:
y.cc:6:12: warning: useless cast to type ‘const int&’ [-Wuseless-cast]
using B::B;
^
y.cc: At global scope:
y.cc:9:8: note: synthesized method ‘D::D(const int&) [inherited from B]’ first
required here
D d2 = 0;
^
>From gcc-bugs-return-562382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 21:02:32 2017
Return-Path: <gcc-bugs-return-562382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52406 invoked by alias); 2 May 2017 21:02:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52344 invoked by uid 48); 2 May 2017 21:02:28 -0000
From: "jens.maurer at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80599] -Wuseless-cast triggers for inherited constructor
Date: Tue, 02 May 2017 21:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jens.maurer at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80599-4-p02ZdY4NSa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00232.txt.bz2
Content-length: 213
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80599
--- Comment #1 from Jens Maurer <jens.maurer at gmx dot net> ---
This is a duplicate of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70844 ;
please close.
>From gcc-bugs-return-562384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 21:32:08 2017
Return-Path: <gcc-bugs-return-562384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69221 invoked by alias); 2 May 2017 21:32: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 69129 invoked by uid 48); 2 May 2017 21:32:03 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70844] spurious -Wuseless-cast warning with inherited constructors
Date: Tue, 02 May 2017 21:32: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: 6.1.0
X-Bugzilla-Keywords:
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-70844-4-OJREFvrFdU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00234.txt.bz2
Content-length: 180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70844
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
*** Bug 80599 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-562383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 21:32:08 2017
Return-Path: <gcc-bugs-return-562383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69208 invoked by alias); 2 May 2017 21:32: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 69113 invoked by uid 48); 2 May 2017 21:32:03 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80599] -Wuseless-cast triggers for inherited constructor
Date: Tue, 02 May 2017 21:32: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80599-4-IKyEdqoJhi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00233.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80599
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
.
*** This bug has been marked as a duplicate of bug 70844 ***
>From gcc-bugs-return-562385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 21:53:49 2017
Return-Path: <gcc-bugs-return-562385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120406 invoked by alias); 2 May 2017 21:53: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 117508 invoked by uid 48); 2 May 2017 21:53:42 -0000
From: "peter at cordes dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80568] x86 -mavx256-split-unaligned-load (and store) is affecting AVX2 code, but probably shouldn't be.
Date: Tue, 02 May 2017 21:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: peter at cordes dot ca
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-80568-4-gpfFLxslWA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00235.txt.bz2
Content-length: 2171
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80568
--- Comment #2 from Peter Cordes <peter at cordes dot ca> ---
Using ISA-extension options removes some microarchitectures from the set of
CPUs that can run the code, so it would be appropriate for them to have some
effect on tuning.
A "generic AVX2 CPU" is much more specific than a "generic x86-64 CPU". For
example, rep ret is useless with -mavx, since PhenomII doesn't support AVX (or
SSE4, actually).
As it stands now, gcc doesn't have a way to tune for a "generic avx2 CPU".
(i.e. only try to avoid problems on Haswell, Skylake, KNL, Excavator, and
Ryzen. Don't care about things that are slow on IvyBridge, Steamroller, or
Atom.)
-mtune=haswell tells gcc that bsf/bsr are fast, but that's not the case on
Excavator (at least it isn't on Steamroller). So -mtune=intel or
-mtune=haswell aren't necessarily appropriate, especially if we're just talking
about -mavx, not -mavx2.
---
In the absence of any -mtune or -march options, -mavx could imply
-mtune=generic-avx, the way -march implies a tuning but can be overridden with
-march=foo -mtune=bar.
Or maybe the default -mtune option should be changed to -mtune=generic-isa, so
users can think of it as a tuning that looks at what -m options are enabled to
decide which uarches it can ignore.
It might be easier to maintain if those tune options are limited to only
disabling workaround-options like rep ret and splitting 256b loads/stores.
Or maybe this suggestion would already add too much maintenance work.
---
I don't know whether -mavx256-split-unaligned-load/store is still worth it if
we take SnB/IvB out of the picture. If it helps a lot for Excavator/Zen, then
maybe. It probably hurts for KNL, which easily bottlenecks on decode
throughput according to Agner Fog, so more instructions is definitely bad.
---
I didn't find any related bug reports, searching even on closed bugs for split
unaligned load, or for -mavx256-split-unaligned-load. I did search some
(including in git for the commit that changed this), but didn't find anything.
Thanks for confirming that it was an intentional bugfix.
>From gcc-bugs-return-562386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 22:56:49 2017
Return-Path: <gcc-bugs-return-562386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25766 invoked by alias); 2 May 2017 22:56:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25613 invoked by uid 48); 2 May 2017 22:56:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70844] [6/7/8 Regression] spurious -Wuseless-cast warning with inherited constructors
Date: Tue, 02 May 2017 22:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cf_known_to_work short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-70844-4-Idb8FZdKqE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2017-05/txt/msg00236.txt.bz2
Content-length: 810
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70844
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-05-02
Known to work| |5.4.0
Summary|spurious -Wuseless-cast |[6/7/8 Regression] spurious
|warning with inherited |-Wuseless-cast warning with
|constructors |inherited constructors
Ever confirmed|0 |1
Known to fail| |6.3.0, 7.1.0, 8.0
>From gcc-bugs-return-562387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 02 23:12:57 2017
Return-Path: <gcc-bugs-return-562387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23213 invoked by alias); 2 May 2017 23:12: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 23181 invoked by uid 89); 2 May 2017 23:12:56 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_ASCII_DIVIDERS,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=recompile, nonu, sk:3.13.0-, trisquel
X-HELO: mail-qt0-f173.google.com
Received: from mail-qt0-f173.google.com (HELO mail-qt0-f173.google.com) (209.85.216.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 02 May 2017 23:12:55 +0000
Received: by mail-qt0-f173.google.com with SMTP id c45so125155747qtb.1 for <gcc-bugs@gcc.gnu.org>; Tue, 02 May 2017 16:12:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d\x1e100.net; s 161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ph9gW9hmrr0tW3oy+8QcX0j+V3/f1cHdEyCpp6gyQZo=; b=hnvvjnENy4SJH0SPKtALfRFWPufNqrAgQFfHTDotgcksGAQoB9/nSuj0pDeqWrb9+J ajWVGjxbXhzSsZIwHQahBDtXKkXzF6374ENAJZJbuUknJcWPUV2395caiqVC0g58En2/ gTZwC6clPkWqkSb4olUCh3oCsT7wZ7bXivG9fRQjLKgr12qNSngEIrkX+/rqSNMts2sc +luNXKP1/hSD/GwSdzsS3D67feXZTDCEtBHourLaezKbvjJR9X20JaK8Zjsll3zmD+jC zgRWGOtxTROZyteo1hG/jomz+4fPD+zBaJsfLPlPZx9z0xkYE4DQQSRRbwsmdm/hQ8VC ZEbw=X-Gm-Message-State: AN3rC/6VApQdANCB9RZHscq1uSb41pEjTEUINZrQDpDR30Ls9KewFzVr 7Ny+5B5wroHHJw=X-Received: by 10.200.46.69 with SMTP id s5mr28782132qta.229.1493766775750; Tue, 02 May 2017 16:12:55 -0700 (PDT)
Received: from localhost.localdomain (75-166-101-229.hlrn.qwest.net. [75.166.101.229]) by smtp.gmail.com with ESMTPSA id i123sm177659qkf.40.2017.05.02.16.12.54 (version=TLS1_2 cipherìDHE-RSA-AES128-GCM-SHA256 bits\x128/128); Tue, 02 May 2017 16:12:55 -0700 (PDT)
Subject: Re: -Wformat-truncation outputs emtpy lines instead of source
To: Simon Sobisch <simonsobisch@web.de>
References: <62c01cc0-af7d-d75f-b81d-1892accb5e0e@web.de> <29446058-d3bb-3dbe-7b63-a48fca04d101@gmail.com> <c7387c2c-b94f-35b5-d01c-8ab39f0c6818@web.de>
Cc: gcc-bugs@gcc.gnu.org
From: Martin Sebor <msebor@gmail.com>
Message-ID: <acc9031f-4c45-4baf-cd2e-c2e057f89f6c@gmail.com>
Date: Tue, 02 May 2017 23:12:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <c7387c2c-b94f-35b5-d01c-8ab39f0c6818@web.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
X-SW-Source: 2017-05/txt/msg00237.txt.bz2
Content-length: 5071
On 05/02/2017 02:13 PM, Simon Sobisch wrote:
> I'm responding here as it was "opened" in this list directly.
> You were right, adding -fno-diagnostics-color doesn't show anything
> empty, changing it to -fdiagnostics-color bring the nice colors in - and
> the spaces instead of the code (yes, I've copied it directly from the
> terminal).
>
> I'm on the following machine:
>
> hostname = mymachine-trisquel
> uname -m = x86_64
> uname -r = 3.13.0-116-lowlatency
> uname -s = Linux
> uname -v = #163+7.0trisquel2 SMP PREEMPT Thu Apr 6 13:16:46 UTC 2017
>
> I've just got the latest revision 247521 from branch-gcc-7 and did a
> recompile (this time using the GCC 7 that was previously built) and the
> issue stays.
>
> I've just placed the output into a vim stdin pipe and can see the source
> + its control attributes:
>
> make 2>&1 | vim - -R -c 'set filetype=nomodified nomodifiable nonu'
>
> ^[[01m^[[K../../../cobc/typeck.c:1064:2:^[[m^[[K ^[[01;36m^[[Knote:
> ^[[m^[[K'^[[01m^[[Ksnprintf^[[m^[[K' output between 17 and 63 bytes into
> a destination of size 17
> ^[[01;36m^[[Ksnprintf (buff, (size_t)17,
> "%02d/%02d/%02d%02d%c%02d%c%02d",^M^[[m^[[K
>
> ^[[01;36m^[[K^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
> ^[[01;36m^[[K current_compile_time.day_of_month,^M^[[m^[[K
> ^[[01;36m^[[K~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
> ^[[01;36m^[[K current_compile_time.month,^M^[[m^[[K
> ^[[01;36m^[[K~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
> ^[[01;36m^[[K current_compile_time.year % 100,^M^[[m^[[K
> ^[[01;36m^[[K~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
> ^[[01;36m^[[K current_compile_time.hour, '.',^M^[[m^[[K
> ^[[01;36m^[[K~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
> ^[[01;36m^[[K current_compile_time.minute, '.',^M^[[m^[[K
> ^[[01;36m^[[K~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
> ^[[01;36m^[[K current_compile_time.second)^[[m^[[K;^M
> ^[[01;36m^[[K~~~~~~~~~~~~~~~~~~~~~~~~~~~~^[[m^[[K
>
> The main question is: is this a GCC problem or a Trisquel problem?
> If it is the later is there any option for GCC to recognize this problem?
From the above it looks like GCC does output the text suggesting
that the problem is not in it, but the GCC colorization is not my
area of expertise (I just wrote the -Wformat-truncation warning).
It's strange to me that you can see the tildes but not the plain
text. I would suggest to try a different terminal. Otherwise,
post your question to gcc-help where people who know more about
these things than me can help you.
Martin
>
> Simon
> Am 02.05.2017 um 01:29 schrieb Martin Sebor:
>> On 05/01/2017 01:39 PM, Simon Sobisch wrote:
>>> Hi,
>>>
>>> I've just got GCC7 (build from svn worked like a charm, even if it
>>> took hours but I was warned) and like the new warnings and hints very
>>> much.
>>>
>>> When compiling GnuCOBOL from vcs (sources on mount, therefore the long
>>> path) I got one warning with multiple and very long tilde lines.
>>>
>>> /media/sf_Entwicklung/GnuCOBOL/gnu-cobol-2.0_texi/cobc/typeck.c: In
>>> function 'cb_build_registers':
>>> /media/sf_Entwicklung/GnuCOBOL/gnu-cobol-2.0_texi/cobc/typeck.c:1064:30:
>>> warning: 'snprintf' output may be truncated before the last format
>>> character [-Wformat-truncation=]
>>> snprintf (buff, (size_t)17, "%02d/%02d/%02d%02d%c%02d%c%02d",
>>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> /media/sf_Entwicklung/GnuCOBOL/gnu-cobol-2.0_texi/cobc/typeck.c:1064:2: note:
>>> 'snprintf' output between 17 and 63 bytes into a destination of size 17
>>>
>>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> current_compile_time.second);
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> It looks like the source in the lines between are missing (the number
>>> of tildes is correct).
>>> The source reads:
>>>
>>> snprintf (buff, (size_t)17, "%02d/%02d/%02d%02d%c%02d%c%02d",
>>> current_compile_time.day_of_month,
>>> current_compile_time.month,
>>> current_compile_time.year % 100,
>>> current_compile_time.hour, '.',
>>> current_compile_time.minute, '.',
>>> current_compile_time.second);
>>
>> Hmm, that's quite odd. I'm not able to reproduce this "effect"
>> and I have never seen anything like it. My first thought was
>> that it could be a problem with the terminal you are using (try
>> compiling with -fno-diagnostics-color to see if it improves)
>> but since you presumably copied the error message above from
>> the terminal that's probably not going to help. If it doesn't,
>> can you please create a new bug and attach to it a preprocessing
>> translation unit (compile the source file with -E and save the
>> output)? Also include the full set of command line options you
>> invoked the compiler with when you got the "invisible" message.
>>
>> [...}
>>
>> Martin
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-05-02 20:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-68491-4@http.gcc.gnu.org/bugzilla/>
2017-05-02 20:37 ` [Bug target/68491] libgcc calls __get_cpuid with 0 level breaks on early 486 uros 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).