https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
Bill Schmidt changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
Bill Schmidt changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80179
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80287
--- Comment #3 from Bernd Edlinger ---
fixed on trunk.
It's theoretically possible that gcc-6-branch is also affected,
but I have not tried.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80287
--- Comment #2 from Bernd Edlinger ---
Author: edlinger
Date: Mon Apr 17 20:41:40 2017
New Revision: 246955
URL: https://gcc.gnu.org/viewcvs?rev=246955&root=gcc&view=rev
Log:
017-04-17 Bernd Edlinger
PR c++/80287
* class.c (f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
--- Comment #6 from Bill Schmidt ---
OK, thanks. I am trying with --disable-werror now, and hopefully that's all
there is to it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
--- Comment #5 from Markus Trippelsdorf ---
(In reply to Bill Schmidt from comment #4)
> (In reply to Markus Trippelsdorf from comment #3)
> > I always use --disable-werror to get past these (harmless) warnings.
>
> Is that harmless, though? 18
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80386
--- Comment #4 from Dmitry Babokin ---
Any update? This bug makes gcc ubsan implementation almost unusable on any real
application.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
--- Comment #4 from Bill Schmidt ---
(In reply to Markus Trippelsdorf from comment #3)
> I always use --disable-werror to get past these (harmless) warnings.
Is that harmless, though? 18446744073709551608 seems like a lot of zeros. :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80415
Jason Merrill changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80415
--- Comment #2 from Jason Merrill ---
Author: jason
Date: Mon Apr 17 19:39:00 2017
New Revision: 246954
URL: https://gcc.gnu.org/viewcvs?rev=246954&root=gcc&view=rev
Log:
PR c++/80415 - wrong error with default arg and array reference.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54924
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
See A
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
--- Comment #2 from Bill Schmidt ---
Well, not a 7 regression, this is actually an improvement over GCC 6, where we
fail during the profile-generate stage...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
Bill Schmidt changed:
What|Removed |Added
Target||powerpc64le-linux-gnu
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
--- Comment #1 from Bill Schmidt ---
Created attachment 41208
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41208&action=edit
Configuration log
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80447
Bug ID: 80447
Summary: Profiled LTO bootstrap fails on powerpc64le
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70167
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80440
--- Comment #2 from Paul Thomas ---
Author: pault
Date: Mon Apr 17 18:22:03 2017
New Revision: 246952
URL: https://gcc.gnu.org/viewcvs?rev=246952&root=gcc&view=rev
Log:
2017-04-17 Paul Thomas
PR fortran/80440
* module.c (find
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80428
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79430
--- Comment #33 from Thomas Koenig ---
> Could you tell me how just to run a single testcase?
Well, I figured that one out.
Quite interesting, a different error with valgrind:
| Events: event normalization mode '1'
==49974== Source and destin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80346
--- Comment #16 from Martin Sebor ---
Interestingly, GCC manages to eliminate the memset at -O1 (and thus avoid
warning) but not at -O2:
$ gcc -O1 -S -Wall -Wextra -Wpedantic -fdump-tree-optimized=/dev/stdout ../b.c
;; Function f (f, funcdef_no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80441
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79430
--- Comment #32 from Thomas Koenig ---
Running your testsuite on powerpc64-unknown-linux-gnu
with a current trunk and "make -k check" gets me
PASS: mlm_matching_isr.run
but also a few more failures:
FAIL: bloch_vectors.run
FAIL: processes.run
Hi
This email (gcc-bugs@gcc.gnu.org) was specified as the recipient of the
transfer.
Find the bill enclosed with this email. Transfer will be posted in 5 hours.
File Pwd: WyaSWslP
Kindest regards
Malesuada Vel Convallis Limited
5.4.52097448.0.65433gcc-bugs@gcc.gnu.org.docx
Description: Attac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80315
--- Comment #7 from kelvin at gcc dot gnu.org ---
Author: kelvin
Date: Mon Apr 17 16:16:43 2017
New Revision: 246949
URL: https://gcc.gnu.org/viewcvs?rev=246949&root=gcc&view=rev
Log:
gcc/testsuite/ChangeLog:
2017-04-12 Kelvin Nilsen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202
--- Comment #10 from Thiago Macieira ---
> But that's what this bug report is for - to make the intrinsicsalways
available.
I never asked for them to be available in undecorated functions. Yes, that's
how both the Intel and Microsoft compilers b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66240
--- Comment #6 from Denis Vlasenko ---
Patches v7 are posted:
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00720.html
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00721.html
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00722.html
https://gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202
--- Comment #9 from Jeffrey Walton ---
On Mon, Apr 17, 2017 at 11:04 AM, glisse at gcc dot gnu.org
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202
>
> --- Comment #8 from Marc Glisse ---
> (In reply to Jeffrey Walton from comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80434
--- Comment #3 from Merri ---
I bumped up the memory and it now works. thank you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80446
Bug ID: 80446
Summary: UNRESOLVED: 18_support/launder/1.cc compilation failed
to produce executable
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Keywords: re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202
--- Comment #8 from Marc Glisse ---
(In reply to Jeffrey Walton from comment #7)
> It appears the intrinsics are not available.
They are available for functions compiled for a suitable target, for instance
because of -march or thanks to the targ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80434
--- Comment #2 from Merri ---
1024 MB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80121
--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to janus from comment #5)
> In trans-decl.c there is a function called 'init_intent_out_dt', which takes
> care of deallocating the allocatable components of intent(out) derived-type
> dum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80121
--- Comment #5 from janus at gcc dot gnu.org ---
In trans-decl.c there is a function called 'init_intent_out_dt', which takes
care of deallocating the allocatable components of intent(out) derived-type
dummies. However, it has a comment saying:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57202
--- Comment #7 from Jeffrey Walton ---
Please forgive my ignorance... What was fixed?
The problem statement is/was "Please make all headers for intrinsics be
includable without special compiler flags." But it appears the intrinsics are
not avail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79430
--- Comment #31 from Thomas Koenig ---
(In reply to Bijan Chokoufe from comment #30)
`bzip2 -d diff.bz2`) as I have no idea what to look for:
> https://cloud.bijancn.de/index.php/s/ta2XMIVWhTUGAvX
Thanks. I looked, but didn't find anything...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
--- Comment #8 from graham.stott at btinternet dot com ---
Original message
From: "trippels at gcc dot gnu.org"
Date: 17/04/2017 12:36 (GMT+00:00)
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80445] /usr/include/c++/6.3.1/cst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
Markus Trippelsdorf changed:
What|Removed |Added
Resolution|FIXED |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
Anton Kochkov changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #7 from Anton Kochkov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
--- Comment #5 from Anton Kochkov ---
Created attachment 41205
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41205&action=edit
preprocessed file
output of
g++ -c -pipe -m32 -O2 -std=gnu++11 -D_REENTRANT -Wall -W -fPIC -D__IDP__
-D__QT__
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
--- Comment #4 from Anton Kochkov ---
here is /usr/include/qt5/QtCore/qbytearray.h:
#ifndef QBYTEARRAY_H
#define QBYTEARRAY_H
#include
#include
#include
#include
#include
#include
#include// <-- line 52
#include
Seem no namespace
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
--- Comment #3 from Markus Trippelsdorf ---
(In reply to Markus Trippelsdorf from comment #2)
> Almost certainly not a gcc bug.
QT must be doing something weird like:
namespace std {
#include
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
--- Comment #1 from Anton Kochkov ---
Forgot to mention command line:
g++ -c -pipe -m32 -O2 -std=gnu++11 -D_REENTRANT -Wall -W -fPIC -D__IDP__
-D__QT__ -D__EA64__ -D__LINUX__ -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB
-DQT_CORE_LIB -I. -I../../
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80445
Bug ID: 80445
Summary: /usr/include/c++/6.3.1/cstdio:124:11: error: ‘::gets’
has not been declaredusing ::gets;
Product: gcc
Version: 6.3.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80426
Eric Botcazou changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80444
Bug ID: 80444
Summary: -fcompare-debug failures with
-fsanitize-coverage=trace-pc
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80443
Marc Glisse changed:
What|Removed |Added
Keywords||ice-on-valid-code
Status|UNCON
* Don Viszneki:
> I'm using standard Ubuntu releases of gcc (5.4.0) and gdb (7.11.1) and I
> have a very simple to reproduce issue on x86-64.
>
> I think I've included all the necessary information in this paste:
>
> https://gist.github.com/hdon/3f96a8a6b67e078e0213660ec6245677
This is likely a l
52 matches
Mail list logo