From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
krebbel@linux.ibm.com, jakub@redhat.com
Subject: Re: [PATCH] S/390: Improve storing asan frame_pc
Date: Tue, 02 Jul 2019 13:34:00 -0000 [thread overview]
Message-ID: <3CC32047-1B4E-46E5-B3DE-B53B870CD565@linux.ibm.com> (raw)
In-Reply-To: <20190702131957.GJ18316@gate.crashing.org>
> Am 02.07.2019 um 15:19 schrieb Segher Boessenkool <segher@kernel.crashing.org>:
>
> On Tue, Jul 02, 2019 at 08:02:16AM -0500, Segher Boessenkool wrote:
>> On Tue, Jul 02, 2019 at 10:51:54AM +0200, Ilya Leoshkevich wrote:
>>> +#undef TARGET_INSN_ALIGNMENT
>>> +#define TARGET_INSN_ALIGNMENT 16
>>
>> There already is FUNCTION_BOUNDARY for something similar, which fits in
>> well with STACK_BOUNDARY, PARM_BOUNDARY, many more *_BOUNDARY. I realise
>> you may prefer a hook, but as long as we aren't getting rid of all the
>> other macros, what's the point?
>
> And maybe LABEL_BOUNDARY is bettter for this than INSN_BOUNDARY as well?
Can’t we just use FUNCTION_BOUNDARY then?
I think .LASANPC is always emitted at the beginning of a function.
Best regards,
Ilya
next prev parent reply other threads:[~2019-07-02 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:52 Ilya Leoshkevich
2019-07-02 13:02 ` Segher Boessenkool
2019-07-02 13:20 ` Segher Boessenkool
2019-07-02 13:34 ` Ilya Leoshkevich [this message]
2019-07-02 13:40 ` Jakub Jelinek
2019-07-02 13:56 ` Ilya Leoshkevich
2019-07-02 14:26 ` Segher Boessenkool
2019-07-03 21:49 ` Richard Sandiford
2019-07-04 11:18 ` Ilya Leoshkevich
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=3CC32047-1B4E-46E5-B3DE-B53B870CD565@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=krebbel@linux.ibm.com \
--cc=segher@kernel.crashing.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).