public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: Petar Jovanovic <petar.jovanovic@rt-rk.com>,
	       "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	       "Moore,
	Catherine (Catherine_Moore@mentor.com)"        
	<Catherine_Moore@mentor.com>
Subject: RE: [PATCH v2][MIPS] fix CRT_CALL_STATIC_FUNCTION macro
Date: Fri, 06 Feb 2015 12:23:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.11.1502061210200.22715@eddie.linux-mips.org> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235320FCAD06@LEMAIL01.le.imgtec.org>

On Fri, 6 Feb 2015, Matthew Fortune wrote:

> >  Native systems have <sys/asm.h> for such ABI dependencies, including
> > stuff to set up $gp.  Perhaps we could reuse these bits, the licence I
> > think allows us to.
> 
> That's a good idea. Perhaps I should take that on as part of some cleanup
> of the MIPS backend in the next stage1. I'm looking to rework how the
> ISA_HAS logic works so perhaps there would be value in doing this mostly in
> a header that can also be used for assembly programmers. That would naturally
> mean we get all the other nice assembly macros available in the backend of
> GCC too.

 This consideration made me realise I've had a patch outstanding for some 
10 years to convert all the `BAL x' instructions there to `BLTZAL $0, x'.  
This has always been a good idea in case implementations recognised the 
special case and avoided involving branch prediction, and I believe it has 
become even more apparent with r6 calling it NAL.

 I'll see if I can submit it to glibc soon -- as you may have been aware 
10 years ago wasn't exactly the most friendly period in glibc maintenance 
and hence I wasn't very prompt with patch submissions.

  Maciej

  reply	other threads:[~2015-02-06 12:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <003e01d04179$ccc38bc0$664aa340$@rt-rk.com>
2015-02-05 20:51 ` Matthew Fortune
2015-02-06 10:43   ` Maciej W. Rozycki
2015-02-06 10:57     ` Matthew Fortune
2015-02-06 12:23       ` Maciej W. Rozycki [this message]
2015-02-06 17:27         ` Mike Stump
2015-02-06 17:41           ` Matthew Fortune
2015-02-06 18:03             ` Mike Stump
2015-02-06 19:19               ` Maciej W. Rozycki
2015-02-06 17:46           ` Maciej W. Rozycki
2015-02-06 15:12   ` Moore, Catherine
2015-02-13  0:28     ` Petar Jovanovic
2015-02-13  1:36       ` Moore, Catherine
2015-04-16 16:53         ` Petar Jovanovic
2015-04-16 18:23           ` Maciej W. Rozycki
2015-04-16 20:38             ` Moore, Catherine
     [not found] <6a22-55314b00-5-5cf51280@159592552>
2015-04-17 18:23 ` Petar Jovanovic
2015-04-17 18:35   ` Moore, Catherine
2015-04-21 18:05     ` Petar Jovanovic
2015-04-17 19:36 ` Maciej W. Rozycki

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=alpine.LFD.2.11.1502061210200.22715@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=Catherine_Moore@mentor.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=petar.jovanovic@rt-rk.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).