https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109869
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109868
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109866
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109862
--- Comment #1 from Richard Biener ---
I think IVOPTs never considers candidates of different size. One could use
niter info to bound the value range (or use ranger) and add a candidate based
on that. But you have to be careful with targets th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109859
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109883
Bug ID: 109883
Summary: Stack Overflow in functions with
types
Product: gcc
Version: 13.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109610
Kewen Lin changed:
What|Removed |Added
CC||linkw at gcc dot gnu.org
--- Comment #12 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109858
--- Comment #9 from Kewen Lin ---
(In reply to Kewen Lin from comment #6)
> (In reply to Hongtao.liu from comment #5)
> > (In reply to Kewen Lin from comment #3)
> > > (In reply to Hongtao.liu from comment #2)
> > > > Does https://gcc.gnu.org/pi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90663
--- Comment #10 from Andrew Pinski ---
Created attachment 55097
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55097&action=edit
Patch which I am testing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106900
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106708
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jiu Fu Guo :
https://gcc.gnu.org/g:5eb7d560626e427673c53723ed430c4bb5721f33
commit r14-923-g5eb7d560626e427673c53723ed430c4bb5721f33
Author: Jiufu Guo
Date: Sat Dec 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109858
--- Comment #8 from Hongtao.liu ---
(In reply to Segher Boessenkool from comment #7)
> > The patch will still use GENERAL_REGS when hard_regno_mode_ok for mode and
> > GENERAL_REGS(which is the case in PR109610), hope it can also fix this
> > re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109880
Peter Bergner changed:
What|Removed |Added
Target Milestone|--- |14.0
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #14 from GARY.WHITE at ColoState dot edu ---
Clarification on the last post. I'm compiling everything with -O3, except
va09ad.f90. If va09ad.f90 is compiled with -O3, you get the bug. If
va09ad.f90 is compiled with -O0, the code p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #12 from GARY.WHITE at ColoState dot edu ---
I just checked, and the bug occurs with the LAPACK routines instead of LinPack.
So "make type=markLAPACK" will generate markLAPACK that will fail with -O3,
but work with -O0.
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #12 from GARY.WHITE at ColoState dot edu ---
I just checked, and the bug occurs with the LAPACK routines instead of LinPack.
So "make type=markLAPACK" will generate markLAPACK that will fail with -O3,
but work with -O0.
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109812
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4079
Andrew Pinski changed:
What|Removed |Added
Known to work||8.1.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109882
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109881
--- Comment #2 from John Marino ---
I found the problematic line.
I changed this line:
data_in := read_compressed_data (input_stream, planned, bytes_read);
to:
bytes_read := read_compressed_data (input_stream => input_stream,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43616
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |5.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109882
--- Comment #3 from Andrew Pinski ---
Then you should file this bug upstream with the sanitizer for the way
__has_feature is handled incorrectly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109882
Andrew Pinski changed:
What|Removed |Added
Component|libstdc++ |sanitizer
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109882
--- Comment #1 from Andrew Pinski ---
__has_feature is being added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109879
Gaius Mulley changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68086
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|tree-optimization
--- Comment #3 from An
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109879
--- Comment #3 from CVS Commits ---
The master branch has been updated by Gaius Mulley :
https://gcc.gnu.org/g:509eef9314b24eff20a5dbdd92f6ab52e2c0c786
commit r14-920-g509eef9314b24eff20a5dbdd92f6ab52e2c0c786
Author: Gaius Mulley
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109882
Bug ID: 109882
Summary: -fsanitize=thread #include transitively
includes sanitizer/common_interface_defs.h
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Seve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79148
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-05-16
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109812
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #11 from GARY.WHITE at ColoState dot edu ---
I've never used valgrind -- what would it do?
The problem isn't that the code is wrong -- otherwise -O0 would not generate
correct results. The compiler is optimizing something incorrect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109881
--- Comment #1 from John Marino ---
I commented out the "file_to_file_decompression" function and the GNAT BUG
disappeared.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66890
--- Comment #6 from Andrew Pinski ---
Really for this loop, I would have assume to be split into 3 different loops
like:
volatile int count;
int main()
{
int i;
for (i = 0; i < 999; i++) {
if (i == 999)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109881
Bug ID: 109881
Summary: GNAT BUG DETECTED during RTL pass, raised
TYPES.UNRECOVERABLE_ERROR
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109805
--- Comment #12 from Sergio Durigan Junior ---
Sorry, I have been busy with other things, but I'm paying attention to the
developments here.
I still have to test the workaround I suggested (passing -fdebug-prefix-map to
LDFLAGS) more broadly, b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109880
Bug ID: 109880
Summary: [14 regression]
gcc.target/powerpc/fold-vec-extract-int.p8.c fails
after r14-916-g9417b30499ce09
Product: gcc
Version: 14.0
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
--- Comment #10 from Steve Kargl ---
On Tue, May 16, 2023 at 03:55:51PM +, Gary.White at ColoState dot edu
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109865
>
> --- Comment #9 from GARY.WHITE at ColoState dot edu dot edu> ---
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109879
Gaius Mulley changed:
What|Removed |Added
Last reconfirmed||2023-05-16
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109879
Gaius Mulley changed:
What|Removed |Added
CC||gaius at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109879
Bug ID: 109879
Summary: ReadCard and ReadInt from WholeIO have problems with
leading space
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106900
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094
--- Comment #26 from Jonathan Wakely ---
Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094
John David Anglin changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109814
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #24 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109570
Christophe Lyon changed:
What|Removed |Added
CC||clyon at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
--- Comment #6 from Jakub Jelinek ---
That is generally the case for the standard C/C++ attributes (arguments just
need to be a balanced token sequence), but not for GNU attributes. Although,
all standard C/C++ attributes we support right now o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33578
--- Comment #10 from Jonathan Wakely ---
For std::this_thread::yield() we do:
inline void
yield() noexcept
{
#if defined _GLIBCXX_HAS_GTHREADS && defined _GLIBCXX_USE_SCHED_YIELD
__gthread_yield();
#endif
}
And gthr-win32.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
--- Comment #5 from Iain Sandoe ---
(In reply to Jakub Jelinek from comment #4)
> (In reply to Andrew Pinski from comment #2)
> > This style of attributes is bad. Because the GNU style attribute is just
> > token(expression,expression,expression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77579
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|pinskia at gcc do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
--- Comment #20 from palmer at gcc dot gnu.org ---
(In reply to rvalue from comment #19)
> (In reply to Aurelien Jarno from comment #18)
> > I wonder if the following patch should also be backported, as it
> > doesn't make sense to link with -lat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109878
Bug ID: 109878
Summary: missed simplifications of MAX and
MIN
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109774
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109774
--- Comment #4 from CVS Commits ---
The releases/gcc-13 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:22741a09a8cbf8a360e99e530b016233dd705ce4
commit r13-7337-g22741a09a8cbf8a360e99e530b016233dd705ce4
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
--- Comment #3 from Iain Sandoe ---
(In reply to Andrew Pinski from comment #2)
> This style of attributes is bad. Because the GNU style attribute is just
> token(expression,expression,expression) it seems odd that they added these
> kind of att
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98202
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #32 from Jonathan Wakely ---
Hmm, yes. Well I think we can at least make std::is_integral<__int128> true,
which will remove once source of surprises for users.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
--- Comment #19 from rvalue ---
(In reply to Aurelien Jarno from comment #18)
> I wonder if the following patch should also be backported, as it
> doesn't make sense to link with -latomic anymore with inline subword atomic
> operations
Agreed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44015
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bkoz at gcc dot g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40094
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bkoz at gcc dot g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40380
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bkoz at gcc dot g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21772
Andrew Pinski changed:
What|Removed |Added
Assignee|bkoz at gcc dot gnu.org|unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9780
Andrew Pinski changed:
What|Removed |Added
Assignee|bkoz at gcc dot gnu.org|unassigned at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18571
Andrew Pinski changed:
What|Removed |Added
Assignee|bkoz at gcc dot gnu.org|unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=5499
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bkoz at gcc dot gn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16006
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bkoz at gcc dot g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33578
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|bkoz at gcc dot g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109774
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:f25d2de17663a0132f9fe090dee39d3b1132067b
commit r14-919-gf25d2de17663a0132f9fe090dee39d3b1132067b
Author: Marek Polacek
Date: Tue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
--- Comment #2 from Andrew Pinski ---
This style of attributes is bad. Because the GNU style attribute is just
token(expression,expression,expression) it seems odd that they added these kind
of attributes without thinking maybe it would be rejec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
--- Comment #18 from Aurelien Jarno ---
Thanks Patrick for working on that and for the backport to the gcc-13 branch. I
wonder if the following patch should also be backported, as it doesn't make
sense to link with -latomic anymore with inline s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
Iain Sandoe changed:
What|Removed |Added
Blocks||90709
Assignee|unassigned at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877
Bug ID: 109877
Summary: Support for clang-style attributes is needed to parse
Darwin SDK headers properly
Product: gcc
Version: unknown
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #31 from joseph at codesourcery dot com ---
It can be an extended integer type in C2x, but then stdint.h would be
required to have int128_t / uint128_t / int_least128_t / uint_least128_t
typedefs, and integer constant suffixes would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55610
Iain Sandoe changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44107
Iain Sandoe changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41991
Bug 41991 depends on bug 44107, which changed state.
Bug 44107 Summary: gcc emits frame (epilogue) info incompatible with the darwin
{8,9}-unwinder,10-compacter
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44107
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
--- Comment #4 from Marek Polacek ---
On trunk we no longer create a static temporary var for { 1, 2 }, because the
code in finish_compound_literal is now guarded by '&& fcl_context == fcl_c99'
but it's fcl_functional here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101118
--- Comment #20 from Iain Sandoe ---
leaving open, I think this might also be needed on 10.x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
Iain Sandoe changed:
What|Removed |Added
Target Milestone|13.2|10.5
--- Comment #17 from Iain Sandoe --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105599
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101118
--- Comment #19 from CVS Commits ---
The releases/gcc-11 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:72f004746d87f01e5e3872af3214e3fa1b48dfa8
commit r11-10788-g72f004746d87f01e5e3872af3214e3fa1b48dfa8
Author: Iain Sandoe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #16 from CVS Commits ---
The releases/gcc-11 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:f4ad0b2287a334613f570c69b7c5320a5a7d7554
commit r11-10785-gf4ad0b2287a334613f570c69b7c5320a5a7d7554
Author: Iain Sandoe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98202
--- Comment #3 from Jonathan Wakely ---
With GCC 13 it's now a pedwarn:
f128.cc:1:1: warning: 'f128' or 'F128' suffix on floating constant only
available with '-std=c++2b' or '-std=gnu++2b' [-Wpedantic]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104871
--- Comment #4 from CVS Commits ---
The releases/gcc-11 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:3417f095f149ba09ca9d4f62bfaf661819a04333
commit r11-10782-g3417f095f149ba09ca9d4f62bfaf661819a04333
Author: Simon Wright
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105599
--- Comment #7 from CVS Commits ---
The releases/gcc-11 branch has been updated by Iain D Sandoe
:
https://gcc.gnu.org/g:a8307cfd66d29efae9c28f5b32bd677398c92dfe
commit r11-10780-ga8307cfd66d29efae9c28f5b32bd677398c92dfe
Author: Iain Sandoe
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772
--- Comment #5 from Jonathan Wakely ---
That would be great :-)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39985
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104772
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|janis at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #30 from Jonathan Wakely ---
(In reply to John Maddock from comment #26)
> (In reply to jos...@codesourcery.com from comment #25)
> > On Thu, 20 Nov 2014, john at johnmaddock dot co.uk wrote:
> >
> > > While we're opening cans of wor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
--- Comment #3 from Andrew Pinski ---
What fixed it on the GCC 8 branch?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
Marek Polacek changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
Andrew Pinski changed:
What|Removed |Added
Known to fail||9.1.0, 9.5.0
Last reconfirmed|2023-05
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
Bug ID: 109876
Summary: initializer_list not usable in constant expressions in
a template
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109623
--- Comment #3 from Marek Polacek ---
// PR c++/109623
struct U {
U() { }
};
struct S {
constexpr S() = default;
U u;
};
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23867
Andrew Pinski changed:
What|Removed |Added
Assignee|mark at codesourcery dot com |unassigned at gcc dot
gnu.org
1 - 100 of 164 matches
Mail list logo