hould
> be changed. Does anybody who knows the ABI know how to fix this?
Do you have any test cases? I'm pretty sure this works, at least in
the usual cases.
A wild guess says that you're doing this in Ada. It may be something
specific to the nested case then.
--
Daniel Jacobowitz
CodeSourcery
and submit for review after testing etc.
Won't be me, I'm afraid - I don't know how this code works, just that
it does in our testing. Sorry.
--
Daniel Jacobowitz
CodeSourcery
hat there is benefit.
Note that only building from a checkout requires flex and bison;
release tarballs do not.
--
Daniel Jacobowitz
CodeSourcery
ere are a few special cases, e.g. for std::string and
std::basic_string; the C++ ABI documents have the details.
_ZSi -> std::basic_istream >
--
Daniel Jacobowitz
CodeSourcery
On Mon, Nov 26, 2007 at 04:29:35PM -0800, Joe Buck wrote:
> But why are you using -fleading-underscore?
It's the default for a lot of targets. I'd still like to see a
concrete example of the problem...
--
Daniel Jacobowitz
CodeSourcery
F files is a
> non-sequitur.
Please give them a little credit. I would assume they're using an
i386-elf compiler and have some mechanism of their own to make the ELF
files run.
--
Daniel Jacobowitz
CodeSourcery
fly...)
It didn't violently not-fly either; I think we persuaded everyone, but
I haven't been back to submit the obvious patch at the end of that
thread yet.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Nov 28, 2007 at 01:56:58PM -0500, Stephane Hockenhull wrote:
> hence my question: where is it?
In libstdc++. You have to link with libstdc++ to use the STL, for
many reasons including this one.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Nov 28, 2007 at 03:38:50PM -0500, Stephane Hockenhull wrote:
> On Wednesday 28 November 2007 14:01, 'Daniel Jacobowitz' wrote:
> > On Wed, Nov 28, 2007 at 01:56:58PM -0500, Stephane Hockenhull wrote:
> > > hence my question: where is it?
> >
> > In l
at
> comment into the svn commit message.
Or even into the ChangeLog...
I've worked on other projects that did this. I found it incredibly
helpful.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Mar 01, 2006 at 06:20:53PM +, Steven Newbury wrote:
> OK, thank-you. I'll target "arm-iwmmxt-linux-gnueabi" with --with-cpu= etc
> and
> --disable-multilib. The vendor string is for my build scripts and also will
> help differentiate the toolchain, is th
nsiderably more efficient than requiring setup of a new
copy-on-write page table.
--
Daniel Jacobowitz
CodeSourcery
On Mon, Dec 10, 2007 at 11:35:15PM +0100, Andreas Schwab wrote:
> Glibc will map vfork to fork in a multithreaded environment.
LinuxThreads used to. NPTL does not; this caused various trouble for
GDB at the time.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Dec 12, 2007 at 11:42:23PM +0100, J.C. Pizarro wrote:
> They are gaming or playing with the words of the language for Google.
This is absurd and off-topic. Please stop.
--
Daniel Jacobowitz
CodeSourcery
endor extension - so I don't
see the problem.
--
Daniel Jacobowitz
CodeSourcery
have one vendor extension, why switch? The vendor
extensions conflict with other vendors... that's by definition.
--
Daniel Jacobowitz
CodeSourcery
On Sun, Dec 16, 2007 at 07:20:37PM -0300, Lucas Prado Melo wrote:
> Why does it happen?
This list is for the development of GCC. Try gcc-help or some other
programming forum, please.
--
Daniel Jacobowitz
CodeSourcery
rking. DWARF has no
trouble handling this sort of thing.
--
Daniel Jacobowitz
CodeSourcery
f course.
>
> I don't think it is fine, we have constant complaints from our
> users about this. I think we definitely need an optimization
> level that avoids this.
It's fine because it's not the problem he's working on. We don't have
to fix everything at once!
--
Daniel Jacobowitz
CodeSourcery
to bad debug
info this may be a limitation in GDB; it does not know anything about
DW_TAG_interface_type.
--
Daniel Jacobowitz
CodeSourcery
t dwarf_tag_name() does know about interface types.
That's just a complete transcription of the DWARF tags (at some point
in history).
--
Daniel Jacobowitz
CodeSourcery
usly correct answer.
For once, I do. As far as a debugger dares to distinguish, any
location is always the beginning of the next instruction, not the end
of the preceeding instruction. If you want to see the zeroes, stop in
probe1 and say "up" instead of "finish".
A hypotheti
s it's some kind of symbol,
probably. There's a default: in the DIE processing that, strictly
speaking, ought not to be there.
--
Daniel Jacobowitz
CodeSourcery
barrassing.
I am pretty sure such an extension has already been proposed. Might
want to check with the committee (see dwarf.org).
--
Daniel Jacobowitz
CodeSourcery
ber the precedence. +
and *, sure, you learn that in grade school. && and || is trickier
because there are sensible arguments for both directions; it is
harder to derive from first principles.
If you are more bothered by any clarifying parentheses than I am,
use -Wno-parentheses.
--
Daniel Jacobowitz
CodeSourcery
e the link time IO problem.
FWIW, in the paragraph you were responding to Ian was talking about
the Darwin system, not the GNU one.
--
Daniel Jacobowitz
CodeSourcery
Oh, I see. Yes, only BFD and GDB know much about it.
--
Daniel Jacobowitz
CodeSourcery
601 - 627 of 627 matches
Mail list logo
