From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H . J . Lu" To: Geoff Keating Cc: libc-hacker@sourceware.cygnus.com, binutils@sourceware.cygnus.com, ian@zembu.com Subject: Re: glibc 2.1 and gabi Date: Thu, 20 Jul 2000 17:10:00 -0000 Message-id: <20000720170946.A7711@lucon.org> References: <20000720114229.A6435@lucon.org> <200007202022.NAA15027@localhost.cygnus.com> <20000720135729.B6994@lucon.org> <200007202246.PAA15150@localhost.cygnus.com> <20000720155245.A7435@lucon.org> <200007202312.QAA15206@localhost.cygnus.com> X-SW-Source: 2000-07/msg00343.html On Thu, Jul 20, 2000 at 04:12:05PM -0700, Geoff Keating wrote: > > Date: Thu, 20 Jul 2000 15:52:45 -0700 > > From: "H . J . Lu" > > Cc: libc-hacker@sourceware.cygnus.com, binutils@sourceware.cygnus.com, > > ian@zembu.com > > > For the most parts, the new tags replace the old ones with a little > > twist. They come from the new gABI. > > I guess the question I'm really asking is "when do I need to switch on > these tags? and why can't the linker do it for me?". You can use it when you are certain your C library supports it. Glibc 2.2 is ok. The linker may not know what the runtime linker will do when it sees a known dtag. As more and more new features are added to those new dtags, glibc may need them to work correctly. H.J.