public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	        Paolo Carlini <paolo.carlini@oracle.com>,
	        GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [patch] PR40134, use a linker script on arm-linux to link with 	-lgcc_s  -lgcc
Date: Fri, 10 Jul 2009 07:56:00 -0000	[thread overview]
Message-ID: <20090710073614.GW4462@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <4A56D949.4010900@ubuntu.com>

On Fri, Jul 10, 2009 at 08:01:45AM +0200, Matthias Klose wrote:
> H.J. mentioned not to bother with the dfp library for now. Is the current patch
> good enough for mainline?
> 
>   Matthias
> 

> Index: gcc.c
> ===================================================================
> --- a/src/gcc/gcc.c	(revision 149315)
> +++ b/src/gcc/gcc.c	(working copy)
> @@ -1686,13 +1686,21 @@
>  		"}"
>  #ifdef LINK_EH_SPEC
>  		"%{shared:"
> +#ifdef ENABLE_SHARED_LIBGCC

What are these #ifdefs good for?

Isn't the whole init_gcc_specs routine wrapped in
#if defined(ENABLE_SHARED_LIBGCC) && !defined(REAL_LIBGCC_SPEC)
?

> +		"%{shared-libgcc:", shared_name, " ", static_name, "}"
> +#else
>  		"%{shared-libgcc:", shared_name, "}"
> +#endif
>  		"%{!shared-libgcc:", static_name, "}"
>  		"}"
>  #else
> +#ifdef ENABLE_SHARED_LIBGCC
> +		"%{shared:", shared_name, " ", static_name, "}"
> +#else
>  		"%{shared:", shared_name, "}"
>  #endif
>  #endif
> +#endif
>  		"}}", NULL);
>  
>    obstack_grow (obstack, buf, strlen (buf));


	Jakub

  reply	other threads:[~2009-07-10  7:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  9:10 Matthias Klose
2009-07-07  9:56 ` Jakub Jelinek
2009-07-07 11:51   ` Dave Korn
2009-07-07 12:21     ` Jakub Jelinek
2009-07-07 13:45       ` Dave Korn
2009-07-07 13:52         ` H.J. Lu
2009-07-07 15:30           ` Dave Korn
2009-07-07 15:53             ` H.J. Lu
2009-07-07 13:22   ` Nathan Froyd
2009-07-10  7:01   ` Matthias Klose
2009-07-10  7:56     ` Jakub Jelinek [this message]
2009-07-13 13:43   ` Matthias Klose
2009-09-09 11:24     ` Jakub Jelinek
2009-09-09 12:27       ` Joseph S. Myers
2009-09-09 13:25         ` Jakub Jelinek
2009-09-09 19:50           ` Richard Henderson
2009-09-09 20:56             ` Joseph S. Myers
2009-09-11 17:13       ` Matthias Klose
2009-09-22 12:26         ` [ping] " Matthias Klose
2009-09-22 15:57           ` Andrew Haley
2009-09-24  8:26             ` Matthias Klose
2009-09-24  8:49               ` Andrew Haley
2009-09-24 10:07                 ` Matthias Klose
2009-09-24 10:45                   ` Andrew Haley
2009-10-14 15:15                     ` Richard Earnshaw
     [not found]                     ` <1255527525.4842.29.camel@e200601-lin.cambridge.arm.com>
2009-10-21 14:11                       ` Matthias Klose
2009-10-30  0:22                         ` [ping2] " Matthias Klose
2009-10-30  0:55                           ` Paolo Carlini
2009-11-02 16:02                             ` Matthias Klose
2009-11-02 16:33                               ` Paolo Carlini
2009-11-12 18:21                                 ` Matthias Klose
2009-11-12 18:47                                   ` Paolo Carlini
2009-12-09 10:47                                     ` Matthias Klose
2009-12-09 10:50                                       ` Paolo Carlini
2009-12-09 10:58                                       ` Paolo Carlini
2009-12-11  8:48                                         ` Matthias Klose
2009-12-11 10:00                                           ` Paolo Carlini
2009-12-14  1:34                                             ` Matthias Klose
2009-12-11 10:35                                           ` Joseph S. Myers
2009-11-16 22:47                                   ` Ralf Wildenhues
2009-11-16 22:48                                     ` Paolo Carlini
2009-09-09 18:29 David Edelsohn

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=20090710073614.GW4462@tyan-ft48-01.lab.bos.redhat.com \
    --to=jakub@redhat.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=paolo.carlini@oracle.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).