public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Torbjorn SVENSSON <torbjorn.svensson@st.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       "Joey.Ye@arm.com" <Joey.Ye@arm.com>,
	       Niklas DAHLQUIST <niklas.dahlquist@st.com>,
	       Samuel HULTGREN <samuel.hultgren@st.com>,
	       Christophe LYON <christophe.lyon@st.com>,
	       Christophe MONAT <christophe.monat@st.com>
Subject: Re: [PATCH] Added information about inline assembler in stack calculations (.su files)
Date: Tue, 27 Nov 2018 19:03:00 -0000	[thread overview]
Message-ID: <20181127184030.GZ23873@gate.crashing.org> (raw)
In-Reply-To: <7f229423-5edb-88e8-a5c2-7c9660339255@st.com>

Hi!

On Mon, Nov 26, 2018 at 02:02:49PM +0000, Torbjorn SVENSSON wrote:
> Attached is a small patch that, in case of inline assembler code, 
> indicates that the function stack usage is uncertain due to inline 
> assembler.
> 
> The test suite are using "nop" as an assembler instruction on all 
> targets, is this acceptable or is there a better way to test this?

Maybe see testsuite/gcc.dg/nop.h ?


Segher

  reply	other threads:[~2018-11-27 19:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 14:03 Torbjorn SVENSSON
2018-11-27 19:03 ` Segher Boessenkool [this message]
2018-11-27 19:46   ` Torbjorn SVENSSON
2018-12-07 23:28     ` Segher Boessenkool
2018-12-01  0:16 ` Jeff Law
2018-12-07  7:51   ` Niklas DAHLQUIST
2018-12-08 12:05     ` Segher Boessenkool
2018-12-14  0:31       ` Jeff Law
2018-12-14  8:58         ` Segher Boessenkool

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=20181127184030.GZ23873@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Joey.Ye@arm.com \
    --cc=christophe.lyon@st.com \
    --cc=christophe.monat@st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=niklas.dahlquist@st.com \
    --cc=samuel.hultgren@st.com \
    --cc=torbjorn.svensson@st.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).