This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Memory corruption? (Re: dwarf generates undefined labels in assembler output)


On Fri, 04 Aug 2000, Marco Franzen wrote:
[20000717 on Unixware7]
> Funnily enough, I can reproduce it only with `-save-temps' or `-S',
> although it originally happened without those flags when normally
> building emacs.

If have had another case meanwhile where it depended on the file names
whether cc1plus (rather than cc1 as before) misbehaved or not. The problem
seemed to go away as well when I generated a .ii file for a bug report
and compiled that, but it re-appeared when I compiled the .ii file with
-save-temps. In that case, the misbehaviour was an ICE, but I guess it
could have been anything.

This smells like memory corruption, doesn't it?

I'll try a later snapshot meanwhile, bootstrapping without a previous gcc
and with BOOT_CFLAGS=-O0. 
But if I can't reproduce it then, it won't necessarily mean anything...
-----------------------------------------------------------------
This email is confidential and intended solely for the use of the
individual to whom it is addressed.
Any views or opinions presented are solely those of the author
and do not necessarily represent those of Thyron Limited.
If you are not the intended recipient then please be advised
that you have received this email in error and that any use,
dissemination, forwarding, printing or copying of this email
is strictly prohibited.
If you have received this email in error, please notify the
Thyron IT Administrator on +44 (0)1923 236 050 or
send an email to mail-admin@thyron.com.
Thank You

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]