I goof'd when doing analysis of missed bext cases. For the shift into
the sign bit, then shift into the low bit case (thankfully the least
common), I got it in my brain that the field is at the left shift count.
It's actually at word_size - 1 - left shift count.
One the subtraction is inclu
Thanks a lot for the review and comments.
I am on a short vacation this week. And will respond to all your questions
after I am back the end of this week.
Qing
> On May 19, 2025, at 06:44, Richard Biener wrote:
>
> On Fri, May 16, 2025 at 3:34 PM Qing Zhao wrote:
>>
>> Control this with a ne
> The series LGTM. I didn't check all the tests in detail to be honest :)
Thanks Robin, the tests is similar and expected up to a point.
Pan
-Original Message-
From: Robin Dapp
Sent: Monday, May 19, 2025 7:06 PM
To: Li, Pan2 ; gcc-patches@gcc.gnu.org
Cc: juzhe.zh...@rivai.ai; kito.ch
On 4/15/25 6:31 AM, Alfie Richards wrote:
This change refactors FMV handling in the frontend to allows greater
reasoning about versions in shared code.
Looking at the cp/ changes:
diff --git a/gcc/cp/class.cc b/gcc/cp/class.cc
index c28d9e5b3ab..4f195ae06cd 100644
--- a/gcc/cp/class.cc
+++ b/
在 2025-5-13 17:18, LIU Hao 写道:
Hello,
Attached is a patch for PR 53929, but is also required by PR 80881.
Ping.
Also I just notice that Clang also quotes mangled MSVC++ symbols in this way, at least since Clang 3.5,
so it's accepted by both GAS and LLVM:
(https://gcc.godbolt.org/z/9xjKb4YP6
On Mon, May 19, 2025 at 04:56:38PM -0400, Jason Merrill wrote:
> On 5/19/25 8:27 AM, Nathaniel Shead wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
> >
> > Alternatively could go back to always marking vtables as DECL_EXTERNAL
> > as well but that doesn't seem to be ne
On 5/19/25 1:50 PM, Harald Anlauf wrote:
Hi Jerry,
so contrary to what the name of patch claims (pr120049-final.diff),
it fixes only the case of direct use of iso_c_binding, but not the
indirect one thru the other module, which is the reason for the
original ICE and the PR.
So if you want to pu
This patch adds support for C23's _BitInt for LoongArch.
Though there's not an official psABI definition, our plan
is to have 16-byte alignment for N > 64 and the padding bits
sign/zero-extended when passed between procedures.
One exception would be "unsigned _BitInt(32)". To match the
behavior o
gcc/ChangeLog:
* stor-layout.cc (layout_type): Allow limb_mode to be DImode
while abi_limb_mode is TImode for _BitInt(N), N > 64.
---
gcc/stor-layout.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gcc/stor-layout.cc b/gcc/stor-layout.cc
index 18b5af56124.
The padding bits of _BitInt(N) are undefined in the x86-64 and
the aarch64 ABI. In general, the current lowering and expand process
perform truncations when taking a _BitInt value as input,
while leaving them as-is in the output.
By adding truncation on the output side, we can define psABIs
(e.g.
Hi,
This is a proposition of a _BitInt(N) implementation for LoongArch,
with the following psABI description:
```
=== Fundamental types of N-bit integers
`_BitInt(N)` (as proposed in ISO/IEC WG14 N2763) is a family of integer types
where `N` specifies the exact number of bits used for its repres
On 5/19/25 11:11 PM, Nathaniel Shead wrote:
On Mon, May 19, 2025 at 04:56:38PM -0400, Jason Merrill wrote:
On 5/19/25 8:27 AM, Nathaniel Shead wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
Alternatively could go back to always marking vtables as DECL_EXTERNAL
as well
vxworks' libatomic comes from its libc, and it's missing
__atomic_feraiseexcept. ARM and AArch64 ports call it implicitly in
c11-atomic-exec-[23].c, so these tests fail.
No exceptions are expected to be raised by these tests, so I'm working
around and silencing the failures by defining the miss
Various arm tests, specifically epilog-1.c and fp16-aapcs-*.c, need
-mno-long-calls to match the expected asm outputs on targets that
default to -mlong-calls. fp16-aapcs-2.c has that flag already.
Regstrapped on x86_64-linux-gnu. Also tested with gcc-14 on aarch64-,
arm-, x86-, and x86_64-vxwo
The pr115485.C testcase uses -fPIE, so it needs to state a PIC
requirement.
Regstrapped on x86_64-linux-gnu. Also tested with gcc-14 on aarch64-,
arm-, x86-, and x86_64-vxworks7r2. Ok to install?
for gcc/testsuite/ChangeLog
* g++.target/arm/pr115485.C: Require a pic effective targe
basic_string.h doesn't define the non-w string version of std::stold
when certain conditions aren't met, and then a couple of tests fail to
compile.
Guard the portions of the tests that depend on std::stold with the
conditions for it to be defined.
Regstrapped on x86_64-linux-gnu. Also tested
stdint.h defines uint64_t instead of __uint64_t, so use the former.
__uint64_t is not available on e.g. vxworks.
Regstrapped on x86_64-linux-gnu. Also tested with gcc-14 on aarch64-,
arm-, x86-, and x86_64-vxworks7r2. Ok to install?
for gcc/testsuite/ChangeLog
* gcc.target/aarch64/
vxworks calls cacheTextUpdate instead of __clear_cache.
Adjust the sme/nonlocal_goto_*.c tests for inexact matches.
Regstrapped on x86_64-linux-gnu. Also tested with gcc-14 on aarch64-,
arm-, x86-, and x86_64-vxworks7r2. Ok to install?
for gcc/testsuite/ChangeLog
* gcc.target/aarc
The test calls sysconf but it doesn't require it as it should.
Regstrapped on x86_64-linux-gnu. Also tested with gcc-14 on aarch64-,
arm-, x86-, and x86_64-vxworks7r2. Ok to install?
for gcc/testsuite/ChangeLog
* gcc.dg/vect/vect-early-break_109-pr113588.c: Require sysconf.
---
..
101 - 119 of 119 matches
Mail list logo
