public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: gcc@gcc.gnu.org
Cc: Iain Buclaw <ibuclaw@ubuntu.com>,
	Ian Lance Taylor <iant@google.com>,
	 gcc@gcc.gnu.org
Subject: Re: Merging gdc (GNU D Compiler) into gcc
Date: Tue, 04 Oct 2011 21:47:00 -0000	[thread overview]
Message-ID: <4E8B7D63.3070206@hesbynett.no> (raw)
Message-ID: <20111004214700.kSu3dS_bnXgExkLC9YW2L75gXkfIWxvzkkZk5SsfaJI@z> (raw)
In-Reply-To: <CA+=Sn1nQfOAgH8QobPOJdHRiKxNSGxmxENK8p+EYAsXeR7Jp=Q@mail.gmail.com>

On 04/10/11 21:36, Andrew Pinski wrote:
> On Tue, Oct 4, 2011 at 12:30 PM, Iain Buclaw<ibuclaw@ubuntu.com>  wrote:
>> These patches address two areas of the D language:
>> 1) D calling convention.
>> 2) Naked functions on i386 and x86_64
>>
>> Some work would need to be done on naked functions at least first so
>> that changes required are only to gcc/config. I would be grateful if I
>> could get pointed in the right direction for implementing naked as a
>> function attribute for i386 so all frontends could benefit.
>
> Does D really require a new calling convention?  Also does it really
> require naked support?  I think naked support is a bad idea and people
> who require naked support should be writing an assembly function
> wrapper.
>
> Thanks,
> Andrew Pinski
>


"naked" functions are often useful in embedded systems, and are 
therefore useful (and implemented) on many gcc targets.  It would make 
sense to have the attribute available universally in gcc, if that 
doesn't involve a lot of extra work, even though it is of little use on 
"big" systems (Linux, Windows, etc.).

mvh.,

David


  parent reply	other threads:[~2011-10-04 21:41 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  7:08 Iain Buclaw
2011-10-04  8:41 ` Andrew Haley
2011-10-04 18:19   ` Iain Buclaw
2011-10-06 15:15   ` Iain Buclaw
2011-10-04 14:03 ` Ian Lance Taylor
2011-10-04 19:30   ` Iain Buclaw
2011-10-04 19:37     ` Andrew Pinski
2011-10-04 20:13       ` Iain Buclaw
2011-10-04 23:11         ` Ian Lance Taylor
2011-10-04 21:41       ` David Brown [this message]
2011-10-04 21:47         ` David Brown
2011-10-04 22:51         ` Andrew Pinski
2011-10-05  9:31           ` David Brown
2011-10-05 10:00             ` David Brown
2011-10-05 12:49             ` Andi Kleen
2011-10-05 14:44               ` David Brown
2011-10-05 14:59                 ` David Brown
2011-10-04 20:41     ` Tom Tromey
2011-10-05  0:59     ` Ian Lance Taylor
2011-10-05  4:14       ` Iain Buclaw
2011-10-11 14:05         ` Dave Korn
2011-10-04 16:50 ` Joseph S. Myers
2011-10-04 19:45   ` Iain Buclaw
2011-10-04 19:56     ` Joseph S. Myers
2011-10-06  8:31 ` Walter Bright
2012-04-11 14:12 ` Iain Buclaw
2012-04-13 23:01   ` Dave Korn
2012-05-10  9:37   ` Iain Buclaw
2012-05-10  9:48     ` Richard Guenther
2012-05-10  9:53       ` Iain Buclaw
2012-05-10 11:51         ` Manuel López-Ibáñez
2012-07-21 20:00 ` Florian Weimer
2012-07-24 20:37   ` Iain Buclaw
  -- strict thread matches above, loose matches on Subject: below --
2010-11-08 23:13 Merging gdc (Gnu " Walter Bright
2010-11-09  1:14 ` Joseph S. Myers
2010-11-09  7:22   ` Walter Bright
2010-11-09 13:09     ` Andrew Haley
2010-11-09 13:57       ` Jakub Jelinek
2010-11-09 16:43         ` Joe Buck

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=4E8B7D63.3070206@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=ibuclaw@ubuntu.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).