public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "David Mc Kenna" <mckennad@esatclear.ie>
To: Keith Seitz <keiths@redhat.com>,
	David Mc Kenna <mckennad@esatclear.ie>,
	Insight Maling List <insight@sources.redhat.com>
Subject: Re: Code display question ( RE GCC - save-temps )
Date: Tue, 19 Mar 2002 09:16:00 -0000	[thread overview]
Message-ID: <3c977216.1021.0@esatclear.ie> (raw)

Thanks for the reply,

The target is for arm-elf.
Included is the c source that I am using and 2 bzipped elf files, one with -save-temps
string ( testwst.elf ) and one without ( testwost.elf ) .

Any help is appreciated,
Dave Mc Kenna


>On Fri, 8 Mar 2002, David Mc Kenna wrote:
>
>> When I compile a program without specifying -save-temps with GCC I can view

>> the code in 4 formats under Insight,i.e. Source,Assembly, Mixed and SRC +
ASM.
>> But when I use the -save-temps switch with GCC I am unable to view the source

>> code as mixed, it appears identical to assembly.
>
>I tried this using GNUPro 00r1 gcc, a special internal x86 compiler, and
>stock gcc from RH7.0 against both CVS Insight and 5.1.1 Insight. I'd say
>that this looks like a compiler problem.
>
>I don't have 3.0.x installed anywhere, can you send me an executable (or
>its debug info)? What target?
>
>Keith
>
>
>
Sun Tzu once wrote......
The supreme act of war is to subdue the enemy without fighting....
--
http://www.iol.ie

             reply	other threads:[~2002-03-19 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  9:16 David Mc Kenna [this message]
2002-03-20 13:40 ` Keith Seitz
  -- strict thread matches above, loose matches on Subject: below --
2002-03-19  9:35 David Mc Kenna
2002-03-08  6:22 David Mc Kenna
2002-03-08  9:04 ` Keith Seitz

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=3c977216.1021.0@esatclear.ie \
    --to=mckennad@esatclear.ie \
    --cc=insight@sources.redhat.com \
    --cc=keiths@redhat.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).