https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93262
--- Comment #7 from CVS Commits ---
The master branch has been updated by Florian Weimer :
https://gcc.gnu.org/g:0e29c6f65523dad20068ba69cd03d8f6f82cab41
commit r14-4846-g0e29c6f65523dad20068ba69cd03d8f6f82cab41
Author: Florian Weimer
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
Bug ID: 111928
Summary: Build broken for baremetal targets after
r14-4825-g6a6d3817afa02b
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #10 from John Paul Adrian Glaubitz ---
(In reply to Oleg Endo from comment #9)
> (In reply to John Paul Adrian Glaubitz from comment #8)
> >
> > I built gcc-13 natively with the patch applied with a full bootstrap
> > including stag
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
Bug ID: 111929
Summary: in decompose, at wide-int.h:1049
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
Bug ID: 111930
Summary: aarch64: SME is still not supported.
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111925
--- Comment #1 from yancheng.li at foxmail dot com ---
found discussion from openSUSE:
https://bugzilla.opensuse.org/show_bug.cgi?id=1133281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111923
--- Comment #7 from Stas Sergeev ---
Also I verified your assumption in
comment #5 by this code:
struct A {
struct dummy {
static constexpr const int foo(const int off = offsetof(A, a)) { return
off; }
static constexpr const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848
--- Comment #21 from Jonathan Wakely ---
std::vector should be preferred in C++.
This warning will not drive responsible C++ developers to use alloca, it will
drive them to use std::vector. As Aaron has said, there are cases where people
use a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
--- Comment #5 from Haochen Jiang ---
It is actually a legacy issue from this:
$ cat 2.c
#include
__attribute__ ((target ("no-avx2")))
void foo ()
{
return _mm_empty ();
}
$ x86_64-pc-linux-gnu-gcc -O2 -mavx512f 2.c
It will also fail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111894
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Blocks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111898
Richard Biener changed:
What|Removed |Added
Known to work||11.4.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111905
--- Comment #5 from Richard Biener ---
For the original testcase and foo we do not perform extra unrolling during
vectorization - we just vectorize the already unrolled loop. bar isn't
unrolled so we do as part of vectorization.
With -fopt-inf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111913
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111914
Richard Biener changed:
What|Removed |Added
Component|c |ipa
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111915
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111916
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
Sam James changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111917
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110721
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #4 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111931
Bug ID: 111931
Summary: RISC-V: Trivial optimization of VSETVL PASS
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111925
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
Richard Biener changed:
What|Removed |Added
Summary|Build broken for baremetal |[14 Regression] Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code,
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111820
Richard Biener changed:
What|Removed |Added
Known to fail|14.0|
Summary|[13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #2 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111591
--- Comment #27 from Richard Biener ---
(In reply to Kewen Lin from comment #26)
> (In reply to Richard Biener from comment #25)
> > (In reply to Kewen Lin from comment #24)
[...]
> > Ah, probably the alias-set is determined from the unmangled r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
--- Comment #5 from Eric Botcazou ---
People really should stop spamming the database with bug reports about random
combinations of switches, this is a waste of time and resources for everyone.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111554
Richard Biener changed:
What|Removed |Added
CC||mkuvyrkov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
Eric Botcazou changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
--- Comment #3 from rguenther at suse dot de ---
On Mon, 23 Oct 2023, sjames at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
>
> Sam James changed:
>
>What|Removed |Added
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111908
Alex Coplan changed:
What|Removed |Added
CC||acoplan at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111927
--- Comment #3 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:0c4bd1321a6def5eb44c530e83b01a415633b660
commit r14-4856-g0c4bd1321a6def5eb44c530e83b01a415633b660
Author: Juzhe-Zhong
Date: Mon Oct 23
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111927
--- Comment #4 from JuzheZhong ---
Fixed on trunk. Plz verify it and close it if it is fixed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
Richard Sandiford changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
--- Comment #4 from David Binderman ---
Reduced test case seems to be:
struct LinearSystem {};
template void operator<<(int, LinearSystem) {
long vars = new long[vars + 2];
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
Eric Botcazou changed:
What|Removed |Added
Summary|[12/13/14 Regression] |[12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
--- Comment #5 from Andrew Pinski ---
My bet it was the c++ change
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=dad311874ac3b3cf4eca1c04f67cae80c953f7b8
or the one right after that one which caused it.
Since it looks like template related
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848
--- Comment #22 from Martin Uecker ---
There may be many good reasons to prefer std::vector over VLAs in C++ but
security and safety is not one of them. There are plenty of CVEs caused by
std::vector out-of-bounds accesses. The question is whet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111927
Huaqi changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111917
--- Comment #7 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:d96bd4aade170fcd86f5f09b68b770dde798e631
commit r14-4857-gd96bd4aade170fcd86f5f09b68b770dde798e631
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111917
Richard Biener changed:
What|Removed |Added
Summary|[11/12/13/14 Regression]|[11/12/13 Regression] ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #1 from Iain Sandoe ---
I'm trying to reproduce this, (and could be making some mistake) but I seem to
see
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
--- Comment #8 from Eric Botcazou ---
The bug is in the (early) SRA pass though;
void h (const struct a i)
{
const short int i$b;
int _1;
short int _2;
int _3;
short int _4;
int _5;
:
i$b_10 = i.b;
i.b = i$b_10;
_1 = g (i)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
Eric Botcazou changed:
What|Removed |Added
Component|ipa |tree-optimization
Assignee|eb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848
--- Comment #23 from Jonathan Wakely ---
(In reply to Martin Uecker from comment #20)
> And what alternative do you think is fundamentally safer than VLAs?
>
> VLAs know their bound. Thus, they integrate with _FORTIFY_SOURCE, and UBSan
> bounds
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848
--- Comment #24 from Jonathan Wakely ---
(In reply to Martin Uecker from comment #22)
> There may be many good reasons to prefer std::vector over VLAs in C++ but
> security and safety is not one of them. There are plenty of CVEs caused by
> std:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111903
--- Comment #4 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:13c0d052478bb45cc97869f5cc333f269aadb36f
commit r14-4858-g13c0d052478bb45cc97869f5cc333f269aadb36f
Author: Andrew Pinski
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111903
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:85e930ac8557c444680b5b29a0a13a14ea6672b5
commit r14-4859-g85e930ac8557c444680b5b29a0a13a14ea6672b5
Author: Andrew Pinski
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111903
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #2 from Dimitar Dimitrov ---
I confirm that build works fine with r14-4820-g11f50716eee812, no maintainer
mode, for pru and arm targets.
I'm using x86_64-pc-linux-gnu build and host machine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #3 from Iain Sandoe ---
(In reply to Dimitar Dimitrov from comment #2)
> I confirm that build works fine with r14-4820-g11f50716eee812, no maintainer
> mode, for pru and arm targets.
>
> I'm using x86_64-pc-linux-gnu build and host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111932
Bug ID: 111932
Summary: Issue Twitter Viral Video Museum 2021 Ngawi Indonesia
Full Terbaru
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #4 from Dimitar Dimitrov ---
If I remove the "AC_CHECK_LIBM" line from libquadmath/configure.ac, and
re-generate autoconf there, then the build passes.
I don't understand why that line was added. Just a few lines below I see checks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
--- Comment #6 from Andrew Pinski ---
Better reduced testcase:
```
template
void f(__SIZE_TYPE__ var) {
new int[var + 2];
}
```
And yes if you change f into an non-template, there is no crash.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #5 from Dimitar Dimitrov ---
> thanks, please could you post your configure line?
$ /mnt/nvme/dinux/local-workspace/gcc/configure
--prefix=/mnt/nvme/dinux/local-workspace/arm-opt --target=arm-none-eabi
--with-newlib --enable-langu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #6 from Iain Sandoe ---
(In reply to Dimitar Dimitrov from comment #4)
> If I remove the "AC_CHECK_LIBM" line from libquadmath/configure.ac, and
> re-generate autoconf there, then the build passes.
>
> I don't understand why that li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111914
--- Comment #3 from Richard Biener ---
The issue is we do
setup_one_parameter (copy_body_data *id, tree p, tree value, tree fn,
basic_block bb, tree *vars)
...
/* Make an equivalent VAR_DECL. Note that we must NOT remap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111933
Bug ID: 111933
Summary: memcpy on Xtensa not optimized when n ==
sizeof(uint32_t) or sizeof(uint64_t)
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111929
--- Comment #7 from Andrew Pinski ---
So the C++ front-end produces:
(gdb) p debug_generic_expr(t)
VIEW_CONVERT_EXPR(var) + NON_LVALUE_EXPR <2>
(gdb) p debug_tree(t)
unit-size
align:64 warn_if_not_align:0 symtab:0 alias-set -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111914
--- Comment #4 from Richard Biener ---
Caused by r0-116946-g27eb31c9de20cd I guess. The easiest is to not perform
the load of the unused parameter for VLA types, but we can also perform this
extra load after remapping types.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110848
--- Comment #25 from Martin Uecker ---
I agree that they are not idiomatic C++ and that there exist good reasons why a
programmer may want to avoid them (including standards compliance). But code
not being idiomatic is not a terrible good reas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111916
Richard Biener changed:
What|Removed |Added
CC||jamborm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111934
Bug ID: 111934
Summary: ICE internal compiler error: in
discriminator_for_local_entity, at cp/mangle.cc:2065
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111934
--- Comment #1 from vincenzo Innocente ---
sorry missed the version
gcc version 14.0.0 20231021 (experimental) [master r14-4817-g405a4140fc3] (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111591
Michael Matz changed:
What|Removed |Added
CC||matz at gcc dot gnu.org
--- Comment #28
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111935
Bug ID: 111935
Summary: gcc ICE with risc-v vector intrinsics
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111860
--- Comment #23 from CVS Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:9ed6b22eb4188c57bb3f5cdba5a7effa95395186
commit r14-4861-g9ed6b22eb4188c57bb3f5cdba5a7effa95395186
Author: Tamar Christina
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936
Bug ID: 111936
Summary: std::stacktrace cannot be used in a shared library
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #11 from CVS Commits ---
The master branch has been updated by Oleg Endo :
https://gcc.gnu.org/g:267e369afbb963d8d84d7a9f0cb9fb18672d99a8
commit r14-4862-g267e369afbb963d8d84d7a9f0cb9fb18672d99a8
Author: Oleg Endo
Date: Mon Oct
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111860
Tamar Christina changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #12 from CVS Commits ---
The releases/gcc-13 branch has been updated by Oleg Endo
:
https://gcc.gnu.org/g:4e1320e4af413b7126f3b998096f60f8b7d5cb32
commit r13-7976-g4e1320e4af413b7126f3b998096f60f8b7d5cb32
Author: Oleg Endo
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
--- Comment #7 from CVS Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:538dcde872abba589b3c8a57181bd7f91018c67a
commit r14-4863-g538dcde872abba589b3c8a57181bd7f91018c67a
Author: Iain Sandoe
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111928
Iain Sandoe changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #13 from CVS Commits ---
The releases/gcc-12 branch has been updated by Oleg Endo
:
https://gcc.gnu.org/g:4414818f4e5de54ea3c353e2ebb2e79a89ae211b
commit r12-9938-g4414818f4e5de54ea3c353e2ebb2e79a89ae211b
Author: Oleg Endo
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936
--- Comment #1 from vincenzo Innocente ---
here is a minimal malloc hook that I would like to use
[innocent@patatrack01 ctest]$ cat getStacktrace.cc
#include
std::string get_stacktrace() {
std::string trace;
for (auto & entry : std
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #14 from CVS Commits ---
The releases/gcc-11 branch has been updated by Oleg Endo
:
https://gcc.gnu.org/g:626bb2e165daa88f5c7cd66b9db49f03921474a9
commit r11-11075-g626bb2e165daa88f5c7cd66b9db49f03921474a9
Author: Oleg Endo
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #15 from Oleg Endo ---
(In reply to John Paul Adrian Glaubitz from comment #10)
>
> Do we need anything else before the fix can be merged?
No, should be fine. I'll leave this PR open for a while in case anything else
related pops
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111591
Richard Biener changed:
What|Removed |Added
Assignee|linkw at gcc dot gnu.org |rguenth at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111916
--- Comment #7 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:458db9b6149b2e9bef94ab76909eb914ed9f675a
commit r14-4866-g458db9b6149b2e9bef94ab76909eb914ed9f675a
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111914
Richard Biener changed:
What|Removed |Added
Known to work||14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111914
--- Comment #5 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:738d44348e7392a9f8e370afa3a9d8c24ee080cd
commit r14-4864-g738d44348e7392a9f8e370afa3a9d8c24ee080cd
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111915
--- Comment #6 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:00eb0812e6464307f9f971d2a743d720015e70cf
commit r14-4865-g00eb0812e6464307f9f971d2a743d720015e70cf
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111916
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111915
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111933
--- Comment #1 from Richard Biener ---
uint32_t from_unaligned_u32(uint32_t *unaligned)
{
uint32_t tmp;
tmp = *unaligned;
note this isn't an unaligned access since you dereference a uint32_t pointer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111933
--- Comment #2 from Davide Bettio ---
(In reply to Richard Biener from comment #1)
> uint32_t from_unaligned_u32(uint32_t *unaligned)
> {
> uint32_t tmp;
> tmp = *unaligned;
>
> note this isn't an unaligned access since you dereference
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111591
--- Comment #30 from Richard Biener ---
Created attachment 56175
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56175&action=edit
prototype patch
This is an (untested) fix, API wise needs some cleanup still. It's the most
simple fix that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111937
Bug ID: 111937
Summary: [RISCV][lto][offload] When `NUM_POLY_INT_COEFFS` > 1,
the `poly_xxx` made `lto_input_mode_table` unable to
parse binary gimple data.
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #16 from John Paul Adrian Glaubitz ---
(In reply to Oleg Endo from comment #15)
> (In reply to John Paul Adrian Glaubitz from comment #10)
> >
> > Do we need anything else before the fix can be merged?
>
> No, should be fine. I'll
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936
--- Comment #2 from Jonathan Wakely ---
(In reply to vincenzo Innocente from comment #0)
> it silently compiles with
> [innocent@patatrack01 ctest]$ c++ -O3 -Wall -pthread -fPIC -shared
> -std=c++23 -lstdc++exp getStacktrace.cc
>
> but the symb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96265
Xiao Ma changed:
What|Removed |Added
CC||mxlol233 at outlook dot com
--- Comment #3 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936
--- Comment #3 from Jonathan Wakely ---
The problem is that libstdc++_libbacktrace.a is not compiled with -fPIC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936
Jonathan Wakely changed:
What|Removed |Added
Keywords||link-failure
Assignee|unass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #17 from Oleg Endo ---
(In reply to John Paul Adrian Glaubitz from comment #16)
> Just saw the branch updates, thanks! FWIW, I did observe this issue in
> gcc-13 only but not gcc-11 or gcc-12. But that might be owed to the fact
> th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111919
David Binderman changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #12 from Alberto Luaces ---
It seems to be slightly different:
(gdb) p expr->ts.type
$7 = BT_PROCEDURE
(gdb) p expr->symtree->name
$8 = 0x770244e8 "@1179"
(gdb) p expr->where
$9 = {nextc = 0x0, lb = 0x0}
Maybe it will be clear
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64450
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110721
Sam James changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org
Keywor
1 - 100 of 170 matches
Mail list logo
