https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111972
--- Comment #15 from Andrew Pinski ---
Patch set finally posted:
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/639019.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112823
Andrew Pinski changed:
What|Removed |Added
Keywords||build
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112823
--- Comment #1 from Sam James ---
At some point, I think we should consider using formal Fixes: git trailers or
something to help find missed backports, but that's another story.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112823
Bug ID: 112823
Summary: -Wincompatible-pointer-types errors in
libiberty/simple-object-mach-o.c (missing backport for
gcc-11)
Product: gcc
Version: 14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112801
--- Comment #5 from JuzheZhong ---
Should be fixed on the trunk. Plz verify it and close it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112801
--- Comment #4 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:1461b431da51f80c90c3bea03d587d76e3e50843
commit r14-6069-g1461b431da51f80c90c3bea03d587d76e3e50843
Author: Juzhe-Zhong
Date: Fri Dec 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88088
Eric Gallager changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70819
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743
--- Comment #5 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:e5bbeedcf7020dfa3870d11cf2b85bc048655698
commit r14-6068-ge5bbeedcf7020dfa3870d11cf2b85bc048655698
Author: Pan Li
Date: Thu Nov 30
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112822
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112822
--- Comment #1 from Andrew Pinski ---
>This is a huge C++ program that I have not cut down yet.
I think it didn't attach because it was too big, maybe compress and attach
that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112822
Bug ID: 112822
Summary: [14 regression] ICE: invalid RHS for gimple memory
store after r14-5831-gaae723d360ca26
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112821
Bug ID: 112821
Summary: GNAT issues bug box on mismatched []
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112820
Bug ID: 112820
Summary: vtable not emitted correctly from module when
compiling with -g
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112819
Bug ID: 112819
Summary: rearrange branches to improve code generation
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
--- Comment #3 from Sam James ---
Created attachment 56766
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56766=edit
reduced.i
cvise just finished here with this, not massaged it by hand though
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28278
--- Comment #5 from Jonathan Wakely ---
Created attachment 56765
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56765=edit
Martin's test code
Attaching the test code here, in case the link stops working.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112775
--- Comment #2 from Andrew Pinski ---
Note the workaround is to do just this:
```
template
class A {};
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112775
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112786
--- Comment #3 from Hans-Peter Nilsson ---
(In reply to Richard Biener from comment #2)
> Note they XPASS on the 13 branch as well IIRC.
XPASS without Alex patch? Is that XPASS a typo for FAIL or PASS?
Either way, they FAIL, for ia32 say
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112782
--- Comment #6 from Andrew Pinski ---
My bet is the code for -mfix-r5900 is not expecting the extra labels that is
produced for debuging ...
Anyways as I mentioned if -mfix-r5900 is the issue then it is a gas issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112782
Andrew Pinski changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112782
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112782
--- Comment #3 from Andrew Pinski ---
I thought this was reported beforehand ...
<<< image/gif: EXCLUDED >>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112783
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112783
--- Comment #2 from Andrew Pinski ---
0x0040d178 <+152>: call 0x401280 <__ctype_b_loc@plt>
=> 0x0040d17d <+157>: movsbq (%r15),%rcx
r150x0 0
Seeing if I can reduce it ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #7 from JuzheZhong ---
(In reply to Vineet Gupta from comment #6)
> (In reply to JuzheZhong from comment #5)
>
> > Support VLS codegen with -mrvv-vector-bits and attribute is reasonable to be
> > landed on GCC-14.
>
> I don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #6 from Vineet Gupta ---
(In reply to JuzheZhong from comment #5)
> Support VLS codegen with -mrvv-vector-bits and attribute is reasonable to be
> landed on GCC-14.
I don't think that is the reqmt for this issue. Just defining the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
--- Comment #2 from Andrew Pinski ---
Created attachment 56764
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56764=edit
A little more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
--- Comment #1 from Andrew Pinski ---
Created attachment 56763
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56763=edit
start of reduction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112818
Bug ID: 112818
Summary: [14 regression] ICE when building accel-ppp (error:
conversion of register to a different size in
‘view_convert_expr’, verify_gimple failed)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #5 from JuzheZhong ---
Support VLS codegen with -mrvv-vector-bits and attribute is reasonable to be
landed on GCC-14.
But currently we are busy with fixing bugs (me, Robin, Lixu@eswin, Li
Pan@intel).
You can see gcc-patch list...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112810
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112810
--- Comment #1 from Andrew Pinski ---
Created attachment 56761
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56761=edit
C++14 testcase (removes the auto argument and changes into an explict template)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112651
--- Comment #4 from Vineet Gupta ---
(In reply to JuzheZhong from comment #3)
> The reason we use --param=riscv-autovec-lmul instead of -mvect-lmul which is
> not documented because we don't have ratifed compile option.
>
> I have mentioned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #4 from Andrew Pinski ---
(In reply to Vineet Gupta from comment #3)
> I agree, but what xsimd does is not under our control. Whoever wants to use
> xsimd for whatever reasons, we can allow gcc to be used similarly to llvm
> and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
Vineet Gupta changed:
What|Removed |Added
CC||vineetg at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #2 from Andrew Pinski ---
Note the reality is xsimd was not thought out for SIMD but rather just fixed
length extensions. It seems more like a major shift that needs to happen to
these libraries and stop just thinking fixed length
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
--- Comment #1 from Andrew Pinski ---
>gcc doesn't, which is a bit of pain for downstream projects such as xsimd.
Does it even make sense to define this? Projects like xsimd seems to be good
for fixed length SIMD but it seems to have a broken
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112817
Bug ID: 112817
Summary: RISC-V: RVV: provide a preprocessor macro for VLS
codegen
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112772
--- Comment #4 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:7317275497e10c4a0fb3fbaa6ca87f3463ac124d
commit r14-6066-g7317275497e10c4a0fb3fbaa6ca87f3463ac124d
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
--- Comment #1 from Andrew Pinski ---
Created attachment 56760
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56760=edit
C testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
Andrew Pinski changed:
What|Removed |Added
Summary|internal compiler error: in |[11/12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773
--- Comment #13 from Robin Dapp ---
Mostly an issue because our expander is definitely not prepared to handle that
:)
It looks like aarch64's is, though, and ours can/should be changed then.
aarch64 doesn't need to implement a qi/bi extract
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112816
Bug ID: 112816
Summary: internal compiler error: in extract_insn, at
recog.cc:2804, unrecognizable_insn for
__builtin_signbit
Product: gcc
Version: unknown
zlib zstd
gcc version 14.0.0 20231201 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112772
--- Comment #3 from anlauf at gcc dot gnu.org ---
Created attachment 56758
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56758=edit
Patch for testcase 2
This patch makes the initialization code seen in testcase 2
dependent on the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112814
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112814
Andrew Pinski changed:
What|Removed |Added
See Also||https://github.com/llvm/llv
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112814
Bug ID: 112814
Summary: `Plus , PHI>` is not optimized to just
PLUS
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112813
Bug ID: 112813
Summary: [14 Regression] RISCV ICE: vsetvl pass: in merge at
config/riscv/riscv-vsetvl.cc:1968 on rv32gcv_zvl256b
Product: gcc
Version: 14.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112788
--- Comment #2 from Andrew Macleod ---
(In reply to Kewen Lin from comment #1)
>
> ranger makes use of type precision directly instead of something like
> types_compatible_p. I wonder if we can introduce a target hook (or hookpod)
> to make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111880
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111880
--- Comment #10 from GCC Commits ---
The releases/gcc-11 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:246760b37f1239b3b97c20fb4a914f21154389a3
commit r11-9-g246760b37f1239b3b97c20fb4a914f21154389a3
Author: Harald
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111880
--- Comment #9 from GCC Commits ---
The releases/gcc-12 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:17cbec6e8ea8817b6240837bb1f1bf74f1b9bdcd
commit r12-10022-g17cbec6e8ea8817b6240837bb1f1bf74f1b9bdcd
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112807
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112764
--- Comment #11 from anlauf at gcc dot gnu.org ---
(In reply to martin from comment #10)
> Thanks for the speedy fix! I just thought about a variation, which should
> now with the fix work as well (was not yet able to compile current dev
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027
Andrew Pinski changed:
What|Removed |Added
CC||sadko4u at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112510
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112812
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027
Andrew Pinski changed:
What|Removed |Added
CC||tonyb at cybernetics dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112334
--- Comment #2 from GCC Commits ---
The master branch has been updated by Alexandre Oliva :
https://gcc.gnu.org/g:b8edb812ff4934c609fdfafe2e1c7f932bc18305
commit r14-6062-gb8edb812ff4934c609fdfafe2e1c7f932bc18305
Author: Alexandre Oliva
ary. With other combinations of options the alignment is
correct. Running on x86_64.
Compile options:
gcc -m64 -Wall -O2 -U_FORTIFY_SOURCE -fstack-protector-strong
-fsanitize=address -fno-omit-frame-pointer
Test fails with gcc version 13.2.1 20231201
Configured with: ../gcc/configure --host=x86_64-pc-li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112795
--- Comment #5 from Eric Botcazou ---
Thanks for looking into this, Jakub. IIRC I didn't write this C++ support, it
was already there in Mike's original implementation.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112807
--- Comment #1 from Jakub Jelinek ---
Ah, the problem is that lower_addsub_overflow was written for lowering of
large/huge _BitInt operations, so for .{ADD,SUB}_OVERFLOW where one of the 2
operands is in the x86_64 case at least 129 bit or the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112445
--- Comment #8 from GCC Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:1390bf52c17a71834a1766c0222e4f8a74efb162
commit r14-6060-g1390bf52c17a71834a1766c0222e4f8a74efb162
Author: Vladimir N. Makarov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697
--- Comment #9 from Alexander Monakov ---
... as does inserting a nop before the compare ¯\_(ツ)_/¯
--- d.out.ltrans0.ltrans.slow.s 2023-12-01 18:32:54.255841611 +0300
+++ d.out.ltrans0.ltrans.s 2023-12-01 18:53:04.909438690 +0300
@@
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112795
--- Comment #4 from Jakub Jelinek ---
Created attachment 56754
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56754=edit
gcc14-pr112795.patch
Untested full fix. If we backport at all, I think we could just change the
maybe_const_value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697
--- Comment #8 from Alexander Monakov ---
Thanks, I can reproduce it. It is pretty tricky though. For instance, just
swapping the mov and the compare is enough to make it fast:
--- d.out.ltrans0.ltrans.slow.s 2023-12-01 18:32:54.255841611
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112795
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112811
Bug ID: 112811
Summary: ICE in -fanalyzer in has_null_terminator
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112808
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112802
--- Comment #1 from Jonathan Wakely ---
Patrick has a pending patch to improve those adaptors.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112795
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103533
--- Comment #10 from GCC Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:83b210d55b28461e7604068c5df95a24b21e7081
commit r14-6056-g83b210d55b28461e7604068c5df95a24b21e7081
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112534
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112796
--- Comment #2 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #1)
> This is not a bug in GCC, the C++ standard allows any header to include any
> other.
See [res.on.headers] in the C++ standard:
"A C++ header may include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112796
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773
--- Comment #12 from rguenther at suse dot de ---
On Fri, 1 Dec 2023, rdapp at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773
>
> --- Comment #11 from Robin Dapp ---
> When I define a vec_extract...bi pattern we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112728
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #3 from Jorn Wolfgang Rennecke ---
> (In reply to Rainer Orth from comment #0)
>> The gcc.dg/scantest-lto.c FAILs on quite a number of targets:
> ...
>> * On Darwin, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112760
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112760
Jakub Jelinek changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #4 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773
--- Comment #11 from Robin Dapp ---
When I define a vec_extract...bi pattern we don't enter the if (vec_extract) in
expmed because e.g.
bitsize = {1, 0}
bitnum = {3, 4}
and GET_MODE_BITSIZE (innermode) = {1, 0} with innermode = BImode.
This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112760
Jakub Jelinek changed:
What|Removed |Added
Summary|[14 Regression] wrong code |[14 Regression] wrong code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112431
--- Comment #9 from GCC Commits ---
The trunk branch has been updated by Lehua Ding :
https://gcc.gnu.org/g:4418d55bcd1b7e0ef823981b6a781d7de5c38cce
commit r14-6054-g4418d55bcd1b7e0ef823981b6a781d7de5c38cce
Author: Juzhe-Zhong
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112431
--- Comment #10 from GCC Commits ---
The trunk branch has been updated by Lehua Ding :
https://gcc.gnu.org/g:a23415d7572774701d7ec04664390260ab9a3f63
commit r14-6055-ga23415d7572774701d7ec04664390260ab9a3f63
Author: Juzhe-Zhong
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112777
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112810
Bug ID: 112810
Summary: bogus ambiguous overload resolution when taking
address of static/xobj member function template
introduced by using declaration where candidates have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112753
Jakub Jelinek changed:
What|Removed |Added
Assignee|jakub at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773
--- Comment #9 from Robin Dapp ---
Ok, it's not the fold_extract_last expander. It just appeared that way here
because I disabled some other things.
What we want to do is extract the last element from a vector. This works as
long as we have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112740
--- Comment #11 from Richard Biener ---
The only thing that's maybe suspicious is that
machine_mode mode = GET_MODE (target);
but we test
/* Use sign-extension for uniform boolean vectors with
integer modes.
linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-6051-20231201105652-gb1fe98dee21-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231201 (exp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112644
Tamar Christina changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112644
--- Comment #6 from Tamar Christina ---
Matthew has been working on this and so far has concluded:
Summary of main problem:
New libhwasan runtime libraries have added interceptors for various mem*, str*
functions (and I think others -- I do
1 - 100 of 143 matches
Mail list logo
