From: Segher Boessenkool <segher@kernel.crashing.org>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: 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:02:00 -0000 [thread overview]
Message-ID: <20190702130216.GI18316@gate.crashing.org> (raw)
In-Reply-To: <20190702085154.26981-1-iii@linux.ibm.com>
Hi Ilya,
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?
Segher
next prev parent reply other threads:[~2019-07-02 13:02 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 [this message]
2019-07-02 13:20 ` Segher Boessenkool
2019-07-02 13:34 ` Ilya Leoshkevich
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=20190702130216.GI18316@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=iii@linux.ibm.com \
--cc=jakub@redhat.com \
--cc=krebbel@linux.ibm.com \
/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).