Shadow Call Stack can be used to protect the return address of a
function at runtime, and clang already supports this feature[1].
To enable SCS in user mode, in addition to compiler, other support
is also required (as discussed in [2]). This patch only adds basic
support for SCS from the compiler
On 2/15/22 10:02, Richard Sandiford wrote:
Dan Li writes:
Shadow Call Stack can be used to protect the return address of a
Looks good, thanks. However, when I bootstrap it on
aarch64-linux-gnu I get:
.../gcc/ubsan.cc: In function ‘bool
ubsan_expand_null_ifn(gimple_stmt_iterator*)’:
.../
This pattern converts (trunc_div (convert a) (convert b)) to
(convert (trunc_div a b)) when:
1. type, a, and b all have unsigned integeral types
2. a and b have the same type precision
3. type has type precision at least as larger as a and b
This is useful as wider divisions are typically more ex
> On 19 Feb 2022, at 5:36 PM, Zhao Wei Liew wrote:
>
> This pattern converts (trunc_div (convert a) (convert b)) to
> (convert (trunc_div a b)) when:
>
> 1. type, a, and b all have unsigned integeral types
> 2. a and b have the same type precision
> 3. type has type precision at least as large
Hi Iain,
> I've committed it upstream, and will merge it down in the next sync-up.
great, thanks. I'll keep the patch local until then.
Rainer
--
-
Rainer Orth, Center for Biotechnology, Bielefeld University
Hi!
I messed up some formatting in the doc rts-files in the constructor commit.
Here is a patch fixing that, adding the ABI key in compability, and also
changing
a comment about linking not being possible, that is not true since drive
options were
added.
I built the docs to verify it looks nic
Please disregard the prior patch I sent some minute ago. I spotted an
copy-paste error, corrected bellow:
>From 7f1d849319318a4cfd304279840899f928f9b86d Mon Sep 17 00:00:00 2001
From: Petter Tomner
Date: Sat, 19 Feb 2022 16:01:54 +0100
Subject: [PATCH] jit: Update docs
Update docs concerning li
Hi,
Per our discussion in the bug report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276
We decided to go with the following solution:
1. avoid emitting switch-unreachable warnings for -ftrivial-auto-var-init;
2. adding a new option -Wtrivial-auto-var-init to emit warnings for the
switch-u
Hi,
This is the 2nd patch for fixing pr102276.
Adding -Wtrivial-auto-var-init and update documentation.
Adding a new warning option -Wtrivial-auto-var-init to report cases when
-ftrivial-auto-var-init cannot initialize the auto variable. At the same
time, update documentation for -ftrivial-auto-
Hi,
With the default ptx isa 6.0, we have for uniform-simt-1.c:
...
@%r33 atom.global.cas.b32 %r26, [a], %r28, %r29;
shfl.sync.idx.b32 %r26, %r26, %r32, 31, 0x;
...
The atomic insn is predicated by -muniform-simt, and the subsequent insn does
a warp syn
Hi,
In nvptx_reorg_uniform_simt we have a loop:
...
for (insn = get_insns (); insn; insn = next)
{
next = NEXT_INSN (insn);
if (!(CALL_P (insn) && nvptx_call_insn_is_syscall_p (insn))
&& !(NONJUMP_INSN_P (insn)
&& GET_CODE (PATTERN (insn)) == PARALLEL
Hi,
We currently generate this code for an atomic store:
...
.reg.u32 %r21;
atom.exch.b32 %r21,[%r22],%r23;
...
where %r21 is set but unused.
Use the ptx bit bucket operand '_' instead, such that we have:
...
atom.exch.b32 _,[%r22],%r23;
...
[ Note that the same problem still occurs for this cod
ping?
On Sat, Feb 12, 2022 at 11:12 AM wrote:
>
> From: Chenghua Xu
>
> Hi, all:
>
> This is the v7 version of LoongArch Port. Please review.
>
> We know it is stage4, I think it is ok for a new prot.
> The kernel side upstream waiting for a approval by gcc side,
> if it is blocked by stage4, a
Hi Mike,
Thanks for your review.
On Wed, Feb 16, 2022 at 12:30 PM Mike Stump via Gcc-patches
wrote:
>
> On Jan 28, 2022, at 5:49 AM, chenglulu wrote:
> >
> > gcc/testsuite/
> >
> >* g++.dg/cpp0x/constexpr-rom.C: Add build options for LoongArch.
> >* g++.old-deja/g++.abi/ptrmem.C
14 matches
Mail list logo
