From: Dominik Vogt <vogt@linux.vnet.ibm.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add new hooks ASM_OUTPUT_START_FUNCTION_HEADER ...
Date: Thu, 01 Oct 2015 06:30:00 -0000 [thread overview]
Message-ID: <20151001063010.GA3783@linux.vnet.ibm.com> (raw)
In-Reply-To: <56092A69.5090802@redhat.com>
On Mon, Sep 28, 2015 at 01:54:17PM +0200, Bernd Schmidt wrote:
> On 09/28/2015 11:44 AM, Dominik Vogt wrote:
> >I mean, it's more or less random whether switching to and from the
> >function's section ends up inside the new .machine and
> >.machinemode directives (if the section needs to be switched for
> >this function) or outside (if the assembler code had already
> >switched to the correct section earlier). I assume that .machine
> >and .machinemode have no effect on the section switching, but I'm
> >not completely sure (alignment?).
>
> Still not really following since I don't know anything about s390
> and its directives.
.machine switches the Cpu (like .arch on x86) and .machinemode
switches between Esa and Zarch modes.
> In case you're trying to figure out whether it's possible to use
> the existing macros, please continue doing so.
I don't see any way to use existing hooks for that (because the
constant pool needs to be wrapped inside the hooks and there are
none that do that at the moment).
> However, you probably should add a sentence or two to
> the documentation to specify ordering wrt other parts of the header
> of a function.
Any suggestions where that information should be placed in the
documentation?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
next prev parent reply other threads:[~2015-10-01 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 11:39 Dominik Vogt
2015-09-22 6:49 ` Trevor Saunders
2015-09-22 20:55 ` Jeff Law
2015-09-23 15:08 ` Dominik Vogt
2015-09-24 11:52 ` Bernd Schmidt
2015-09-24 14:18 ` Dominik Vogt
2015-09-25 14:56 ` Bernd Schmidt
2015-09-28 10:23 ` Dominik Vogt
2015-09-28 12:26 ` Bernd Schmidt
2015-10-01 6:30 ` Dominik Vogt [this message]
2015-10-01 9:27 ` Bernd Schmidt
2015-10-16 10:49 ` Dominik Vogt
2015-10-16 10:52 ` Dominik Vogt
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=20151001063010.GA3783@linux.vnet.ibm.com \
--to=vogt@linux.vnet.ibm.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).