On Mon, Apr 28, 2025 at 8:57 PM H.J. Lu wrote:
>
> On x86, both stores with 32-bit immediate and register are supported:
>
>0: 48 c7 40 10 00 00 00 00 movq $0x0,0x10(%rax)
>8: 48 89 50 10 movq %rdx,0x10(%rax)
>
> But store with 32-bit immediate is 4 byte longer.
>
> Add UNSPEC
On Wed, May 7, 2025 at 4:10 AM Richard Biener
wrote:
>
> On Wed, May 7, 2025 at 3:55 AM Andrew Pinski wrote:
> >
> > Like the patch to phiopt (r15-4033-g1f619fe25925a5f7), this adds rewriting
> > of VCE to gimple_with_undefined_signed_overflow/rewrite_to_defined_overflow.
> > In the case of movin
Hi!
When libgfortran is compiled, there are some -Woverflow warnings like
../../../libgfortran/generated/maxloc0_4_m1.c:99:14: warning: unsigned
conversion from ‘int’ to ‘GFC_UINTEGER_1’ {aka ‘unsigned char’} changes value
from ‘-255’ to ‘1’ [-Woverflow]
99 | maxval = -GFC_UINTEGER_1_HUGE
On 5/1/25 7:03 AM, Richard Sandiford wrote:
Indu Bhagat writes:
[...]
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index ffde9df85fd3..de651183a703 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -17079,6 +17079,14 @@ and @option{-fsanitize=kernel-hwaddress}.
To disabl
On Tue, 6 May 2025, SAKSHAM JOSHI wrote:
> I am submitting a patch for the GCC compiler's "stdbool.h" to optimize the
> size of the true and false macros in the C programming language. Currently,
> the size of the true and false macros is 4 bytes, whereas the _Bool
> datatype is 1 byte in size. Th
libstdc++-v3/ChangeLog:
PR libstdc++/120159
* src/c++23/std.cc.in (is_layout_compatible_v): Export.
---
Tested x86_64-linux. Pushed to trunk and gcc-15.
libstdc++-v3/src/c++23/std.cc.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/libstdc++-v3/src/c++23/std.cc.in b/libstd
Indu Bhagat writes:
>>> starting bb 3
>>> 33: {cc:CC=cmp(r121:DI,0x10);r121:DI=r121:DI-0x10;}
>>> 32: r122:DI=r122:DI+0x10
>>> 31: [r122:DI+0]=unspec/v[[r122:DI+0],r120:DI] 17
>>> mem count failure
>>> mem count failure
>>
>> Yeah, we'd need to update auto-inc-dec for this case.
>>
On 5/1/25 12:01 PM, Richard Sandiford wrote:
Indu Bhagat writes:
In context of stack tagging, the AArch64 Memtag ABI Extension to ELF
specifies the usage of two dynamic tags for the dynamic loader to do the
necessary tasks:
- If DT_AARCH64_MEMTAG_MODE is present, the dynamic loader should (i
101 - 108 of 108 matches
Mail list logo