From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Yong <10walls@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] harden-sls-6.c: fix warning on LLP64
Date: Tue, 28 Feb 2023 19:15:46 +0100 [thread overview]
Message-ID: <Y/5E0tSmlMgK/4h9@tucnak> (raw)
In-Reply-To: <1c665816-5815-7bc4-f7ac-859e8c873007@gmail.com>
On Wed, Feb 15, 2023 at 01:44:08PM +0000, Jonathan Yong via Gcc-patches wrote:
> gcc/testsuite/ChangeLog:
>
> * gcc.target/i386/harden-sls-6.c: fix warning on LLP64
> targets.
>
> Attached patch OK?
> From c0572a1e95c6f569980d6b7454c8dc293f07389e Mon Sep 17 00:00:00 2001
> From: Jonathan Yong <10walls@gmail.com>
> Date: Wed, 15 Feb 2023 13:42:12 +0000
> Subject: [PATCH] harden-sls-6.c: fix warning on LLP64
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/i386/harden-sls-6.c: fix warning on LLP64
> targets.
s/fix/Fix/
Otherwise LGTM.
>
> Signed-off-by: Jonathan Yong <10walls@gmail.com>
> ---
> gcc/testsuite/gcc.target/i386/harden-sls-6.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.target/i386/harden-sls-6.c b/gcc/testsuite/gcc.target/i386/harden-sls-6.c
> index 9068eb64008..3b270211927 100644
> --- a/gcc/testsuite/gcc.target/i386/harden-sls-6.c
> +++ b/gcc/testsuite/gcc.target/i386/harden-sls-6.c
> @@ -11,7 +11,7 @@ struct _Unwind_Context {
> struct _Unwind_Context cur_contextcur_context =
> _Unwind_Resume_or_Rethrow_this_context;
> offset(0);
> - __builtin_eh_return ((long) offset, 0);
> + __builtin_eh_return ((__INTPTR_TYPE__) offset, 0);
> }
>
> /* { dg-final { scan-assembler "jmp\[ \t\]+\\*%rcx" } } */
Jakub
next prev parent reply other threads:[~2023-02-28 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 13:44 Jonathan Yong
2023-02-26 5:11 ` NightStrike
2023-02-28 18:15 ` Jakub Jelinek [this message]
2023-03-01 13:43 ` Jonathan Yong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y/5E0tSmlMgK/4h9@tucnak \
--to=jakub@redhat.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).