On Mon, 2025-08-18 at 09:15 +0800, Lulu Cheng wrote:
> Pushed to r16-3247 ... r16-3264.
>
> Sorry it took so long to merge.
> > LoongArch: Implement 16-byte CAS with sc.q
Sorry but it seems we need to revert this one particularly.
The implementation has a bug: in CAS operation if expected !=
On Wed, Aug 13, 2025 at 5:04 AM Palmer Dabbelt wrote:
>
> On Tue, 12 Aug 2025 13:56:09 PDT (-0700), pins...@gmail.com wrote:
> > On Tue, Nov 26, 2024 at 12:54 PM Jeff Law wrote:
> >>
> >>
> >>
> >> On 11/26/24 11:43 AM, Florian Weimer wrote:
> >> > * Jeff Law:
> >> >
> >> >> On 11/26/24 9:06 AM,
based on the technical specification n3589[1], and set behind the
command line flag '-fdefer-ts'
deferred statements execute at the end of the scope they're added on,
similar to the cleanup attribute, and they have much of the same
constraints as statement expressions, with added limitation that n
for future use with defer statements, as they do not have a declaration
associated, and are bound to the scope with a BIND_EXPR
gcc/c/ChangeLog:
* c-typeck.cc (push_cleanup): Adjust.
Signed-off-by: Anna (navi) Figueiredo Gomes
---
gcc/c/c-typeck.cc | 10 --
1 file changed, 8 in
gcc/c-family/ChangeLog:
* c-common.h (D_CXX11): Adjust.
(D_EXT): Likewise.
(D_EXT89): Likewise.
(D_EXT11): Likewise.
(D_ASM): Likewise.
(D_OBJC): Likewise.
(D_CXX_OBJC): Likewise.
(D_CXXWARN): Likewise.
(D_CXX_CONCEPTS): Likew
represent the start and end of scope which a local jump is not allowed
to cross as a jump barrier, moving this logic out into a function allows
for defer statements to use the same codepath
gcc/c/ChangeLog:
* c-decl.cc (struct c_jump_barrier): New structure.
(struct c_spot_binding
* added a test jumping into a defer block from above.
* reworded the lookup_label_for_goto error message to mention the error
is a jump into the defer block, instead of out.
* moved the 'defer' keyword behind a -fdefer-ts flag, and added texinfo
docs plus related failure test.
---
based on n3589[
Pushed to r16-3247 ... r16-3264.
Sorry it took so long to merge.
Thanks!
在 2025/3/1 上午11:46, Xi Ruoyao 写道:
The entire patch bootstrapped and regtested on loongarch64-linux-gnu
with -march=la664, and I've also tried several simple 16-byte atomic
operation tests locally.
OK for trunk? Or maybe
On Sat, Aug 16, 2025 at 5:48 PM H.J. Lu wrote:
>
> We can't place a TLS call before a conditional jump in a basic block like
>
> (code_label 13 11 14 4 2 (nil) [1 uses])
> (note 14 13 16 4 [bb 4] NOTE_INSN_BASIC_BLOCK)
> (jump_insn 16 14 17 4 (set (pc)
> (if_then_else (le (reg:CCNO 17 flag
We can't place a TLS call before a conditional jump in a basic block like
(code_label 13 11 14 4 2 (nil) [1 uses])
(note 14 13 16 4 [bb 4] NOTE_INSN_BASIC_BLOCK)
(jump_insn 16 14 17 4 (set (pc)
(if_then_else (le (reg:CCNO 17 flags)
(const_int 0 [0]))
(label_ref
On 8/15/25 11:54 AM, Austin Law wrote:
PR 121213 shows an unnecessary "li target,0" in an atomic exchange loop
on RISC-V.
The source operand for an amoswap instruction should allow (const_int 0)
in addition to GPRs. So the operand's predicate is changed to
"reg_or_0_operand". The correspon
On 8/13/25 4:57 PM, Aleksandar Rakic wrote:
[PATCH v2 01/12] Testsuite: Fix tests properly for compact-branches:
https://sourceware.org/pipermail/gcc-patches/2025-March/677827.html
Installed.
[PATCH v2 02/12] Fix unsafe comparison against stack_pointer_rtx:
https://sourceware.org/piperm
On 8/13/25 4:57 PM, Aleksandar Rakic wrote:
Thanks a lot for pushing the patch — I really appreciate it.
Regarding MIPS testing, I understand the Jenkins situation and the
limitations it imposes. If any regressions show up, I’ll be happy to
help investigate and provide fixes.
To make thing
On 7/27/25 3:35 AM, Artemiy Volkov wrote:
From: Artemiy Volkov
Consider the following (RISC-V) instruction pair:
mul s6,a1,a2
add s6,a4,s6
Without this patch, while handling the second instruction, (a) the
existing chain for s6 will first be closed (upon the terminate_write
action for the
On 8/17/25 6:38 AM, Jan Dubiec wrote:
This patch fixes genrecog warnings about operands missing modes. This is
done by explicitly specifying modes of operations.
2025-07-17 Jan Dubiec
PR target/109324
gcc/ChangeLog:
* config/h8300/addsub.md: Explicitly specify mode for plus op
This patch fixes genrecog warnings about operands missing modes. This is
done by explicitly specifying modes of operations.
2025-07-17 Jan Dubiec
PR target/109324
gcc/ChangeLog:
* config/h8300/addsub.md: Explicitly specify mode for plus operation.
* config/h8300/jump
The contrib/check-MAINTAINERS.py script sorts by surname, name, bugzilla
handle and email (in this order). Document this. Switch around Andrew
Pinski's entries in Contributing under DCO.
Pushing as obvious.
ChangeLog:
* MAINTAINERS: Switch around Andrew Pinski's entries in
Cont
17 matches
Mail list logo