https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105956
--- Comment #13 from Martin Liška ---
(In reply to tt_1 from comment #12)
> may I ask kindly - this was seemingly reported with a git version of gcc-12,
> so is there still a need for backporting the fix to that branch as well?
No, only the mas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106417
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106315
--- Comment #4 from Levy Hsu ---
So I cross-compared all sizes of those .o files in make.out:
list of all diff > 2% files:
Size1: 19464 Size2: 20760 File: PUGH/SetupPGV.o
Size1: 324675 Size2: 402929 File: LocalReduce/CountFunctions.o
Size1: 37
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106389
--- Comment #6 from Richard Biener ---
(In reply to Marek Polacek from comment #4)
> (In reply to Richard Biener from comment #3)
> > For the rule to take effect the frontend needs to mark each access that
> > falls under the rule as to have ali
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187
--- Comment #34 from Richard Biener ---
(In reply to Richard Earnshaw from comment #33)
> I suspect there is still a question, though, as to whether it is safe in
> general for two objects with non-conflicting alias sets to share a stack
> slot.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106419
--- Comment #3 from Kewen Lin ---
(In reply to Arseny Solokha from comment #2)
> I don't set --enable-default-pie anymore when configuring gcc, so here's the
> difference. Therefore, it stops ICEing if I add -fPIE or -fPIC when
> compiling the t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345
--- Comment #3 from CVS Commits ---
The master branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:75d20d6c84c12bedd65a904e462f02f0b9eb3f77
commit r13-1818-g75d20d6c84c12bedd65a904e462f02f0b9eb3f77
Author: Peter Bergner
Date: Mon J
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106419
--- Comment #2 from Arseny Solokha ---
I don't set --enable-default-pie anymore when configuring gcc, so here's the
difference. Therefore, it stops ICEing if I add -fPIE or -fPIC when compiling
the testcase. Conversely, could you please try addi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106419
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2022-07-25
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106420
--- Comment #4 from zero at smallinteger dot com ---
Sorry about that :/.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106431
--- Comment #1 from Sam James ---
(Ignore the comment about `as` hanging, that's just a side-effect of -pipe,
which I didn't clock at first.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106431
Bug ID: 106431
Summary: Hang when compiling large printf() file (from glibc's
tst-printf-bz18872) on HPPA with -ggdb3
Product: gcc
Version: 11.3.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106420
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106420
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69410
--- Comment #4 from Zopolis0 ---
I believe I've bisected the breaking change to
7655e009c8f506454a5cc16bace7282b67513c00
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429
--- Comment #3 from Andrew Pinski ---
Also almost all of the GCC build scripts depend on just POSIX sh rather than
bash. It might be the case you need to set CONFIG_SHELL instead as defined as
part of the autoconf .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429
--- Comment #2 from Andrew Pinski ---
GCC 11.2.0 had the same as what I found on the trunk `git grep "/bin/bash"
releases/gcc-11.2.0`):
releases/gcc-11.2.0:contrib/bench-stringop:#!/bin/bash
releases/gcc-11.2.0:contrib/compare-all-tests:#! /bin/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106430
Bug ID: 106430
Summary: [modules] ICE on function result of imported type with
user-declared constexpr destructor
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106429
Bug ID: 106429
Summary: Building GCC is Inhibited on old Linux Distributions
due to the use of "#!/bin/bash"
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106425
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106428
Bug ID: 106428
Summary: -Wanalyzer-file-leak false positive with if ((ptr =
fopen(...)) == NULL) ...
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106421
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106421
--- Comment #2 from Andrew Pinski ---
It is undefined but still valid.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106421
--- Comment #1 from Andrew Pinski ---
> The documentation might want to specify that goto from a nested function
It already does.
from
https://gcc.gnu.org/onlinedocs/gcc-12.1.0/gcc/Labels-as-Values.html#Labels-as-Values
:
"You may not use this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103504
--- Comment #2 from anlauf at gcc dot gnu.org ---
The ICE is avoided by:
diff --git a/gcc/fortran/interface.cc b/gcc/fortran/interface.cc
index 7ed6e13711f..f8a1720ea7e 100644
--- a/gcc/fortran/interface.cc
+++ b/gcc/fortran/interface.cc
@@ -280
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106427
Bug ID: 106427
Summary: -Wuse-after-free=3 false alarm about int (not pointer)
variable
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51437
Pavel M changed:
What|Removed |Added
CC||pavel.morozkin at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106426
Bug ID: 106426
Summary: UTF-8 character literals do not have unsigned type in
the preprocessor in -fchar8_t mode
Product: gcc
Version: 9.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106347
--- Comment #5 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:76d6224b944e1a66bfb1195fb7d35d9726f1aed8
commit r13-1811-g76d6224b944e1a66bfb1195fb7d35d9726f1aed8
Author: Roger Sayle
Date: Sun J
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106303
--- Comment #9 from CVS Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:76d6224b944e1a66bfb1195fb7d35d9726f1aed8
commit r13-1811-g76d6224b944e1a66bfb1195fb7d35d9726f1aed8
Author: Roger Sayle
Date: Sun J
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106422
--- Comment #4 from Alexander Monakov ---
Regarding point 1 above, I should mention that Glibc headers mark both 'vfork'
and 'raise' as leaf.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106422
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100107
Rin Okuyama changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106389
--- Comment #5 from Jan Hubicka ---
I agree with Richi that this is not modref bug. It merely exposes the fact that
we intentionally ignore this rule.
For single compilation unit this rule is already problematic since one can not
determine alia
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106425
--- Comment #1 from Martin Uecker ---
Example:
int f(void)
{
auto n = 1.5;
return n * 2;
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106425
Bug ID: 106425
Summary: implicit-int
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at
37 matches
Mail list logo
