From: Ben Elliston <bje@redhat.com>
To: Klaus Pedersen <klaus.kruse.pedersen@mail.tele.dk>
Cc: SID-list <sid@sources.redhat.com>
Subject: Re: Compile problems with GCC 3.0.4
Date: Wed, 24 Apr 2002 07:47:00 -0000 [thread overview]
Message-ID: <15558.50585.458156.462657@tooth.toronto.redhat.com> (raw)
In-Reply-To: <3CC5ED29.2060603@mail.tele.dk>
>>>>> "Klaus" == Klaus Pedersen <klaus.kruse.pedersen@mail.tele.dk> writes:
Klaus> * There are a lot of throw() issues.
Klaus> * A missing deconstructor in mmu/armRemap.cxx
Klaus> * Some namespace problems in sidcpuutils.h
Klaus> Does my changes make any sense, or is it GCC problems?
No, your changes make sense. I am just surprised we had not caught
them before now. I will take a look through your patches in due
course and apply them as necessary. Thanks!
Ben
prev parent reply other threads:[~2002-04-24 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 16:23 Klaus Pedersen
2002-04-24 7:47 ` Ben Elliston [this message]
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=15558.50585.458156.462657@tooth.toronto.redhat.com \
--to=bje@redhat.com \
--cc=klaus.kruse.pedersen@mail.tele.dk \
--cc=sid@sources.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).