https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117646
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117647
--- Comment #2 from Sam James ---
Sorry, to be specific: "gdb bug, hence should be reported on their bugzilla at
sourceware.org/bugzilla instead".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117647
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #1 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117494
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117357
Uroš Bizjak changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #75 from Julian Waters ---
Any feedback on the new patch?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117643
--- Comment #2 from kargls at comcast dot net ---
Created attachment 59617
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59617&action=edit
initial partial implementation
The attached patch is an initial implementation of f_c_string() up t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117418
Hongtao Liu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117646
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117646
Andrew Pinski changed:
What|Removed |Added
Host|x86_64-pc-linux-gnu |
Summary|[15 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117418
--- Comment #5 from Hu Lin ---
Has been backported to gcc12, gcc13 and gcc14.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117646
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117403
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117418
--- Comment #4 from GCC Commits ---
The releases/gcc-14 branch has been updated by Hu :
https://gcc.gnu.org/g:8b4bb54e6c45411845ec559c49f594a6239c3969
commit r14-10937-g8b4bb54e6c45411845ec559c49f594a6239c3969
Author: Hu, Lin1
Date: Wed Nov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69374
--- Comment #28 from GCC Commits ---
The master branch has been updated by John David Anglin :
https://gcc.gnu.org/g:29c4f6637cd604bf993d7309c236ebcdb554a858
commit r15-5373-g29c4f6637cd604bf993d7309c236ebcdb554a858
Author: John David Anglin
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117646
Bug ID: 117646
Summary: [15 Regression] ICE: verify_gimple failed invalid
types for ‘bit_ior_expr’
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: nor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117646
--- Comment #2 from Andrew Pinski ---
The problem is the max(a,b) == 0 match pattern. Let me check what is done for
a==0&a==0 for pointers. I can't remember if there is a convert or not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117599
--- Comment #1 from chenglulu ---
(In reply to Xi Ruoyao from comment #0)
> The ABI needs to be defined:
> https://github.com/loongson/la-abi-specs/issues/13.
Thank you very much, we're already researching it now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26323
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102296
--- Comment #3 from Andrew Pinski ---
Oh the problem is not DECL_SIZE vs TYPE_SIZE (sorry about that) but rather:
sol2.h:
size = int_size_in_bytes (TREE_TYPE (DECL)); \
ASM_OUTPUT_SIZE_DIRECTIVE (FILE, NAME, size);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100258
--- Comment #2 from Andrew Pinski ---
LLVM does:
.LBB0_8:
movl$1065353216, (%rsi)
movl$1065353216, 12(%rsi)
movl$1065353216, 24(%rsi)
movl$1065353216, 36(%rsi)
addq$4, %rdx
add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117616
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117645
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117645
--- Comment #1 from John David Anglin ---
Created attachment 59616
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59616&action=edit
late_combine2 RTL dump
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117645
Bug ID: 117645
Summary: FAIL: gcc.dg/graphite/pr29581-2.c execution test
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116640
--- Comment #2 from Joshua Maiche ---
I thought the inconsistency was just tied to whether the default template
parameter was a dependent name, but even within cases where a private dependent
type is used, there seems to be some inconsistency on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117450
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53357
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117357
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-11-17
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117494
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117644
Bug ID: 117644
Summary: check_vect in tree-vect.h doesn't check RISCV V
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywords: testsuite-fail
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117494
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117494
--- Comment #2 from Andrew Pinski ---
Created attachment 59614
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59614&action=edit
Fix I think
This should fix it. signal is the check that is needed here rather than
`*-*-linux* *-*-gnu* *-*-u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117477
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117402
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103819
--- Comment #10 from Andrew Pinski ---
*** Bug 117429 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117429
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117411
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117411
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117404
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117534
Andrew Pinski changed:
What|Removed |Added
Known to fail||12.3.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117534
--- Comment #1 from Andrew Pinski ---
Specialization of template functions is frowned on.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117235
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117642
Andrew Pinski changed:
What|Removed |Added
Summary|__sync_lock_release() on|[12/13/14/15 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117535
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79137
Michael Meissner changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117571
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117627
John David Anglin changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117627
--- Comment #3 from GCC Commits ---
The master branch has been updated by John David Anglin :
https://gcc.gnu.org/g:8f50a0794076d6e1d4d1ed693b94d6ee2e4cd849
commit r15-5370-g8f50a0794076d6e1d4d1ed693b94d6ee2e4cd849
Author: John David Anglin
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210
Dimitry Andric changed:
What|Removed |Added
CC||dimitry at andric dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
Bug 87403 depends on bug 95445, which changed state.
Bug 95445 Summary: diagnose incompatible calls to functions declared without
prototype [-Wdeprecated-non-prototype]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95445
What|Remov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95445
Florian Weimer changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95445
--- Comment #5 from GCC Commits ---
The trunk branch has been updated by Florian Weimer :
https://gcc.gnu.org/g:701d8e7e60b85809cae348c1e9edb3b0f4924325
commit r15-5369-g701d8e7e60b85809cae348c1e9edb3b0f4924325
Author: Florian Weimer
Date: S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #13 from R. Diez ---
> Those two could be combined into one struct so there's only one destructor
> registration instead of two.
Thanks for your help, but reducing the number of atexit calls doesn't really
help me much. As I said
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117643
--- Comment #1 from kargls at comcast dot net ---
Here's a testcase (obviously untested).
!
! { dg-do run }
!
program foo
use iso_c_binding, only : c_null_char, f_c_string
logical, volatile :: asis
character(len=6, kind=c_char) s1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #12 from Andreas Schwab ---
ld -M or ld --Map=file produces a map file that explains why an object is
needed. There is also --cref.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117643
Bug ID: 117643
Summary: F_C_STRING from F23 is missing
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #11 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #4)
> The remaining global destructors are:
>
> src/c++98/ios_base_init.h:12
> src/c++11/compatibility-c++0x.cc:218
> src/c++11/compatibility-c++0x.cc:218
> src/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #10 from Jonathan Wakely ---
There is a patch under review for GCC 15 which should make the unstable ABI
configuration only support SSO string, eventually (the current patch doesn't do
it, but I would follow up on it).
Building the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116488
--- Comment #13 from Mikael Pettersson ---
And gcc.dg/torture/pr116915.c which was also added for this BZ invokes UB on
int16 targets:
pr116915.c: In function 'main':
pr116915.c:8:20: warning: iteration 32768 invokes undefined behavior
[-Waggre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #9 from Jonathan Wakely ---
The exception types in require a COW string of some kind so that
copies are no except. Since we already have one, that's what we use.
I'd like to have a more lightweight COW string that is A I compatible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106852
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:7db55c0ba1baaf0e323ef7f9ef8c9cda077d40e9
commit r15-5366-g7db55c0ba1baaf0e323ef7f9ef8c9cda077d40e9
Author: Jason Merrill
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #8 from R. Diez ---
I am not sure yet why generic_category_instance and system_category_instance
are not been discarded like they probably should.
I haven't found any way to make the linker say why it is pulling certain
symbols or o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #7 from Jonathan Wakely ---
No, the system_error.cc file uses the other std::string type. It needs to be in
a file using the COW string. It could be in its own file, but why doesn't
linking with --gc-sections avoid pulling it in?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116488
Mikael Pettersson changed:
What|Removed |Added
CC||mikpelinux at gmail dot com
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117642
Bug ID: 117642
Summary: __sync_lock_release() on 128bit integer does not
behave according to documentation
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Keywo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #6 from R. Diez ---
I looked further for anything that references *_category* in my firmware, by
looking at the linker-generated cross-references table, and I noticed this in
file "gcc-14.2.0/libstdc++-v3/src/c++11/cow-stdexcept.cc":
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117641
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-11-17
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114023
federico changed:
What|Removed |Added
CC||federico.perini at gmail dot
com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117641
--- Comment #1 from Andrew Pinski ---
sync_resolve_size should have returned -1 due to this:
if (size == 16
&& fetch
&& !orig_format
&& TREE_CODE (type) == BITINT_TYPE
&& !targetm.scalar_mode_supported_p (TImode))
r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116253
--- Comment #6 from David Malcolm ---
Followup patches:
* [PATCH 1/2] c++: print z candidate count and number them
* https://gcc.gnu.org/pipermail/gcc-patches/2024-November/669035.html
* [PATCH 2/2] diagnostics: suppress "note: " prefix in ne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117641
Bug ID: 117641
Summary: ICE: SIGSEGV in contains_struct_check (tree.h:3788)
with __sync_fetch_and_add() on _BitInt(128) on i686
Product: gcc
Version: 15.0
Status: UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117628
Andrew Pinski changed:
What|Removed |Added
CC||doko at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117640
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116253
--- Comment #7 from David Malcolm ---
Created attachment 59611
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59611&action=edit
Screenshot of textual output with followup patches
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117638
Sam James changed:
What|Removed |Added
Known to work||13.3.1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116813
Sam James changed:
What|Removed |Added
Last reconfirmed||2024-11-17
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117276
--- Comment #10 from Oliver Schönrock ---
Sorry, should have made that clear..
yes, appears to be a regression between gcc-10 and gcc-12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117276
--- Comment #9 from Sam James ---
I suppose the point is that it makes it a regression.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117276
--- Comment #8 from Jonathan Wakely ---
GCC 10 is not supported upstream, so we don't care about it anyway.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117640
Bug ID: 117640
Summary: [15 Regression] error: two or more data types in
declaration specifiers
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117630
--- Comment #5 from R. Diez ---
I am trying to figure out why generic_category_instance and
system_category_instance land in my ELF file even though nobody is apparently
using them. Other similar objects, like io_category_instance, do not.
So I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117638
--- Comment #1 from Sam James ---
(In reply to Sam James from comment #0)
> I see the following:
> * With GCC 13 using -D_GLIBCXX_ASSERTIONS, we split the loop.
> * With GCC 14 and trunk using -D_GLIBCXX_ASSERTIONS, we can't.
> * We don't seem a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117639
Bug ID: 117639
Summary: Modified loop-split-1.C doesn't recognise non-escaping
std::vector
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117638
Bug ID: 117638
Summary: [14/15 regression] No loop splitting and bounds check
not optimized out with -D_GLIBCXX_ASSERTIONS
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117637
Bug ID: 117637
Summary: g++.dg/tree-ssa/loop-split-1.C has undefined behaviour
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210
--- Comment #4 from Sam James ---
I'm not Jonathan but I don't have a particularly useful guess for when this
started. Any chance you'd be willing to bisect it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210
--- Comment #5 from Lorenzo Salvadore ---
(In reply to Vedran Miletic from comment #2)
> Lorenzo, thanks for packaging new versions so regularly. This issue started
> roughly 2-3 versions ago, any ideas why it could be?
Thanks for reporting and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210
--- Comment #3 from Vedran Miletic ---
FWIW, this issue still exists with:
% g++15 --version
g++15 (FreeBSD Ports Collection) 15.0.0 20241110 (experimental)
89 matches
Mail list logo