delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/01/20/07:52:50

To: djgpp AT delorie DOT com
Subject: Re: GCC bugs
References: <01bf611a$9c6e9500$LocalHost AT alex> <3883BCC2 DOT 2CC1DCD9 AT a DOT crl DOT com> <01bf61c3$70f0a7c0$LocalHost AT alex> <Pine DOT SUN DOT 3 DOT 91 DOT 1000119113628 DOT 9609M-100000 AT is> <01bf627f$0b8075c0$LocalHost AT alex>
From: Michael Bukin <M DOT A DOT Bukin AT inp DOT nsk DOT su>
Date: 20 Jan 2000 13:53:29 +0600
In-Reply-To: "Alexei A. Frounze"'s message of "19 Jan 2000 13:19:04 GMT"
Message-ID: <20ya9li3gm.fsf@Sky.inp.nsk.su>
Lines: 17
X-Mailer: Gnus v5.5/Emacs 19.34
Reply-To: djgpp AT delorie DOT com

"Alexei A. Frounze" <alex DOT fru AT mtu-net DOT n-o-s-p-a-m DOT ru> writes:

> But I run command line and batch file in the same(!) directory. Futhermore,
> there are no any DJGPP scripts and such things in this directory. And I
> don't change anything, I just run GCC first way then second way.

Try the following commands from command line and watch the magic of
appearing and disappearing .eh_frame:

bash% gcc -c test.c
bash% gcc -c test.C

Second command tells gcc to use C++ for compilation and it adds this
section for some reason (I guess "eh" means "exception handler").

-- 
Michael Bukin

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019