public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* why the asymmetry in VX_CRT{BEGIN,END}_SPEC?
@ 2021-12-07 15:09 Rasmus Villemoes
  2021-12-08  8:04 ` Olivier Hainque
  0 siblings, 1 reply; 2+ messages in thread
From: Rasmus Villemoes @ 2021-12-07 15:09 UTC (permalink / raw)
  To: Olivier Hainque, gcc

Hi Olivier

One thing I've been meaning to ask: Is there a reason VX_CRTBEGIN_SPEC
and VX_CRTEND_SPEC are given as

#define VX_CRTBEGIN_SPEC "vx_crtbegin.o%s"
#define VX_CRTEND_SPEC "-l:vx_crtend.o"

so for vx_crtbegin.o, it is gcc itself which expands the full path to
the vx_crtbegin.o file, while for vx_crtend.o, the linker is instructed
to go looking for it.

Rasmus

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: why the asymmetry in VX_CRT{BEGIN,END}_SPEC?
  2021-12-07 15:09 why the asymmetry in VX_CRT{BEGIN,END}_SPEC? Rasmus Villemoes
@ 2021-12-08  8:04 ` Olivier Hainque
  0 siblings, 0 replies; 2+ messages in thread
From: Olivier Hainque @ 2021-12-08  8:04 UTC (permalink / raw)
  To: Rasmus Villemoes; +Cc: Olivier Hainque, gcc

Hi Rasmus,

> On 7 Dec 2021, at 16:09, Rasmus Villemoes <rv@rasmusvillemoes.dk> wrote:
> 
> Hi Olivier
> 
> One thing I've been meaning to ask: Is there a reason VX_CRTBEGIN_SPEC
> and VX_CRTEND_SPEC are given as
> 
> #define VX_CRTBEGIN_SPEC "vx_crtbegin.o%s"
> #define VX_CRTEND_SPEC "-l:vx_crtend.o"
> 
> so for vx_crtbegin.o, it is gcc itself which expands the full path to
> the vx_crtbegin.o file, while for vx_crtend.o, the linker is instructed
> to go looking for it.

I don't think there's a reason today and the patchset
I'm working on uses %s consistently.

Cheers,

Olivier


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-12-08  8:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-07 15:09 why the asymmetry in VX_CRT{BEGIN,END}_SPEC? Rasmus Villemoes
2021-12-08  8:04 ` Olivier Hainque

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).