From: Cedric Roux <cedric.roux@acri-st.fr>
To: morrell@alumni.ucsd.edu
Cc: gcc-help@gcc.gnu.org
Subject: Re: temp preprocessed filename
Date: Wed, 03 Mar 2010 09:05:00 -0000 [thread overview]
Message-ID: <4B8E2612.8050202@acri-st.fr> (raw)
In-Reply-To: <761579.83235.qm@web112612.mail.gq1.yahoo.com>
Michael Morrell wrote:
> Luckily(?), this isn't a ccache issue. I was able to reproduce it with
> g++. We're using an ARM cross-compiler from CodeSourcery (Sourcery G++
> 4.3-234).
>
> To reproduce what I'm seeing:
>
> % cat foo.cpp
> #include <cstdlib>
>
> void foo() {}
> % g++ -g -E foo.cpp > foo.ii
> % g++ -g -c foo.ii
> % readelf -wl foo.o | grep foo
> 1 0 0 0 foo.cpp
> 6 0 0 0 foo.ii
>
> There is something in <cstdlib> that is triggering this behavior, but I
> don't know if it is a cstdlib bug or a compiler bug.
>
> I'll file a bug report with CodeSourcery, but was curious if anyone here
> had any thoughts. I will also try to dig into <cstdlib> and see if I
> can isolate this further.
>
> Michael
doing:
% cat foo.cpp
using namespace bar;
does include foo.ii.
When you do readelf -wlLiaprmfFsoR foo.o
(let's be a bit barbarian)
in the .debug_info you see that std is seen
as being declared in foo.ii (DW_AT_decl_file : 2)
(where 2 points to foo.ii) instead of foo.cpp.
Don't know if it's expected behavior but maybe
your problem is this one.
next prev parent reply other threads:[~2010-03-03 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 11:31 Michael Morrell
2010-02-28 4:10 ` Ian Lance Taylor
2010-02-28 21:34 ` Michael Morrell
2010-03-01 18:26 ` Ian Lance Taylor
2010-03-02 21:13 ` Michael Morrell
2010-03-03 9:05 ` Cedric Roux [this message]
2010-03-03 9:35 ` Cedric Roux
2010-03-02 22:05 ` Michael Morrell
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=4B8E2612.8050202@acri-st.fr \
--to=cedric.roux@acri-st.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=morrell@alumni.ucsd.edu \
/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).