https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105857
--- Comment #8 from andysem at mail dot ru ---
I think, sanitizers won't detect it unless you build libstdc++ with them
enabled. I would expect valgrind to detect it though.
I think, Ubuntu builds libstdc++ with _FORTIFY_SOURCE enabled,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105857
--- Comment #3 from andysem at mail dot ru ---
I'm not sure about the meaning of the wrong-code keyword, but just to clear, I
do not consider the code sample in the bug report to be wrong (i.e. incorrect
usage of the standard library). If
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105857
--- Comment #16 from andysem at mail dot ru ---
Thanks for the fix. And for the explanation.
Yes, backport would be nice.
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dushistov at mail dot ru
Target Milestone: ---
Online demo available here https://godbolt.org/z/6jdKK1K7n .
For code like this:
```
enum class MyEnum { A, B, C, D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100570
--- Comment #3 from fsmoke ---
Is any movement about this BUG?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118699
--- Comment #2 from Egor ---
It says 14.2.0. So this is fixed in trunk, I assume...
COLLECT_GCC=Z:\mingw64\bin\g++.exe
COLLECT_LTO_WRAPPER=Z:/home/holyblackcat/.quasi-msys2/mingw64/root/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/14.2.0/l
NCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: MikeSmith32564 at mail dot com
Target Milestone: ---
#include
#include
int main()
{
setenv("STR1", "NAME=VALUE", 1);
ch
rsion: 14.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: iamsupermouse at mail dot ru
Target Milestone: ---
The bug only happens on MinGW.
This code:
#in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113958
Milian Wolff changed:
What|Removed |Added
CC||mail at milianw dot de
--- Comment #5
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: iamsupermouse at mail dot ru
Target Milestone: ---
GCC on Windows has a relatively little-known flag `-fno-ms-extensions`, which
disables some problematic MSVC-like extensions, which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119714
Johannes Larsen changed:
What|Removed |Added
CC||mail at johslarsen dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100570
--- Comment #6 from fsmoke ---
I just now tested my sample on gcc 13.3 it seems bug already fixed somehow
>>That's not a system include directory, because you didn't use -isystem
And no... it's not nesessery, because isystem works for all subd
rmal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jukkaho at mail dot student dot oulu dot fi
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29235
--- Comment #6 from jigorou3 at mail dot goo dot ne dot jp 2007-08-14
17:46 ---
It looks like
zlib compiled w/ -O -msse -ftree-vectorize (built with fedora's rpm package
gcc-4.1.2-17)
has same problem.
In my environment, rpm-4.4.2.1-7.fc8 and seamonkey-1.1.3-6.fc8 segfault
--- Comment #10 from jigorou3 at mail dot goo dot ne dot jp 2007-09-20
10:43 ---
Created an attachment (id=14228)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14228&action=view)
zlib testcase(zlib's inftrees.c)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32893
--- Comment #13 from jigorou3 at mail dot goo dot ne dot jp 2007-09-22
11:28 ---
(In reply to comment #12)
Hmm..., but in my environment, some applications always segfaults at zlib which
was built with -O -msse -ftree-vectorize.
I'm sorry, but now I recognize that I don't h
--- Comment #7 from chris dot pickett at mail dot mcgill dot ca 2008-02-18
00:31 ---
If I ever update SableVM's Classpath and it's still broken I'll reopen it.
However, maybe you should check that the duplicate is also fine:
http://gcc.gnu.org/bugzilla/show_b
--- Comment #5 from chris dot pickett at mail dot mcgill dot ca 2008-03-03
02:55 ---
Maybe you could fix the preprocessor to warn about operators with known side
effects. Can cpp see the entire expr in assert (expr)? If so, just search the
tokens for =, ++, --, +=, -=, etc
2.6.28.6 ends with a segfault
Product: gcc
Version: 4.1.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: lasse-gccbug-2009 at mail dot plastictree dot net
GCC
--- Comment #1 from lasse-gccbug-2009 at mail dot plastictree dot net
2009-04-04 22:27 ---
Created an attachment (id=17588)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17588&action=view)
Preprocessed source file
The file is over 1 MB when uncompressed.
--
--- Comment #2 from lasse-gccbug-2009 at mail dot plastictree dot net
2009-04-04 22:29 ---
Created an attachment (id=17589)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17589&action=view)
Kernel configuration which triggers the problem
Maybe this can help.
The problem i
--- Comment #3 from lasse-gccbug-2009 at mail dot plastictree dot net
2009-04-05 15:19 ---
Segfault does not occur when omitting '-ffreestanding'.
Segfault does not occur when using '-save-temps'.
When I add '-save-temps' to 'arch/x86/Make
--- Comment #5 from lasse-gccbug-2009 at mail dot plastictree dot net
2009-04-23 06:42 ---
(In reply to comment #4)
> Can you give the output of gcc -v?
>
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with:
/package/host/localhost/sepbuilt/gcc41-4.1.2-01-03/src/
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gnu at tzik dot jp
Target Milestone: ---
In the repro case below, `foo()` in `co_return false ? co_await foo() : 1;`
should not be evaluated, and we should not see "NOTREACHED&
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gnu at tzik dot jp
Target Milestone: ---
In a repro case below, `co_await ({auto x = future{}; x;});` causes an internal
compiler error.
https://wandbox.org/permlink/3jX83p34mVDfBgc1
The
IRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gnu at tzik dot jp
Target Milestone: ---
In a repro case below, the lambda is wrongly handled as a constexpr and its
co_return causes a compile error,
--- Additional Comments From chris dot pickett at mail dot mcgill dot ca
2005-01-12 14:03 ---
Thank-you kindly. Can you summarize your solution?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16203
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: noobie-iv at mail dot ru
Target Milestone: ---
Created attachment 57404
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57404&action=edit
Test prog
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113896
--- Comment #9 from noobie-iv at mail dot ru ---
I confirm that the original bug in the scantailor-experimental project was also
fixed by commit 2f16c53558d01135f0f78cf78a2f722b774684d7.
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gcc at nh2 dot me
Target Milestone: ---
GCC currently lacks good compile-time warnings that help find common integer
overflow bugs.
For example, the code
#include
void f(uint64_t n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110933
--- Comment #1 from Niklas Hambüchen ---
A tangentially related issue is bug 24542 which is about another common
overflow bug, the pattern "u64 = u32 * u32".
Just linking it here because people interested in solving integer overflow
issues may
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24542
--- Comment #15 from Niklas Hambüchen ---
Another common integer overflow bug type is the "for (u32 i = 0; i < u64; ++i)"
pattern, as well as general widening comparisons.
I filed bug 110933 for those; just linking it here for people interested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101361
Taiju Tsuiki changed:
What|Removed |Added
CC||mail+gnu at tzik dot jp
--- Comment #12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101361
--- Comment #13 from Taiju Tsuiki ---
I saw a similar inaccurate -Wstringop-overread warning with a smaller
reproducer (attached).
https://wandbox.org/permlink/EPjH0ZPoA4EWky0e
Reproducing gcc was tip of trunk (
https://github.com/gcc-mirror/gc
: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: mail+gcc at nh2 dot me
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Please see:
"Why does my OpenMP app sometimes use only 1 thread, sometimes 3, sometimes all
cores?"
https://stackov
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: chris dot pickett at mail dot mcgill dot ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29774
--- Comment #2 from chris dot pickett at mail dot mcgill dot ca 2006-11-09
04:46 ---
I got confused. It's only the enum constant that must be int. Indeed, if the
comparison is `if (FOO >= 0)', no warning is issued and all is well.
Thanks for the extremely fast response!
: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: chris dot pickett at mail dot mcgill dot ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30437
--- Comment #3 from chris dot pickett at mail dot mcgill dot ca 2007-01-14
06:06 ---
I don't think that's the right explanation.
cc1: error: unrecognized command line option "-Wno-all"
...
--enable-languages=c
...
gcc version 4.3.0 20070110 (experimental)
Althoug
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: a-horohorin at mail dot ru
Target Milestone: ---
Hi,
I have found a performance bug on RISC-V target.
Example:
```c
int main() {
int arr[5000];
for (int i = 0; i < 5000; ++i) {
arr[i]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116904
--- Comment #1 from Andrey Khorokhorin ---
`-fpic` flag solves the problem, but it seems like a workaround, but not a
solution
Summary: gfrotran and cc1 error
Product: gcc
Version: 4.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: kih at mail dot nerc-essc dot ac d
--- Comment #3 from kih at mail dot nerc-essc dot ac dot uk 2008-05-23
20:45 ---
Subject: RE: gfrotran and cc1 error
Hi
Thanks for the response. I was actually installing software on someone
else's system (with their permission) which was an apple machine. I will
chec
--- Comment #4 from kih at mail dot nerc-essc dot ac dot uk 2008-05-23
20:52 ---
Subject: RE: gfrotran and cc1 error
Hi
'gfortran -v' and 'gcc -v' report:
gfortran -v
Using built-in specs.
Target: powerpc-apple-darwin8
Configured with: /Builds/apple
--- Comment #6 from kih at mail dot nerc-essc dot ac dot uk 2008-05-27
19:57 ---
Subject: RE: gfortran and cc1 error
The distribution came from:
http://r.research.att.com/tools/
so I guess I should take it up with them.
Regards
Kevin
-Original Message-
From: fxcoudert at
--- Comment #6 from pmoulder at mail dot csse dot monash dot edu dot au
2010-05-12 05:29 ---
Part of the problem is a documentation bug: the nonnull attribute's parameter
is named "arg-index", suggesting that the first parameter is 0, while the
example strongly suggests
--- Comment #8 from pmoulder at mail dot csse dot monash dot edu dot au
2010-05-12 09:25 ---
OK, on careful reading, I agree re memcpy etc. (see below).
Consequently, I amend my suggested change to the documentation to:
- Add a sentence about implicit `this' argument (c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110956
--- Comment #6 from ro at manam dot mail-host-address-is-not-set ---
> --- Comment #3 from Rainer Orth ---
> (In reply to Thomas Neumann from comment #1)
>> The assert says that the code tries to de-register a frame that it did not
1001 - 1048 of 1048 matches
Mail list logo
