From: Aldy Hernandez <aldyh@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com, jason@redhat.com
Subject: Re: sid doesn't build with gcc 4.0.x
Date: Fri, 01 Jul 2005 10:45:00 -0000 [thread overview]
Message-ID: <20050701104534.GA25446@redhat.com> (raw)
In-Reply-To: <20050630202058.GA7997@redhat.com>
> > * component/interrupt/components.h (bus_size): Fix constructor to
> > be legitimate C++.
>
> This one is ok, feel free to commit.
Done, thanks.
>
> > * component/cgen-cpu/cgen-cpu.h (GETMEMSF): Change
> > reinterpret_cast to static_cast.
> > (SETMEMSF): Same.
> > (GETMEMDF): Same.
> > (SETMEMDF): Same.
>
> This one is not (but I will commit a better one).
I just checked the new snapshot, and gcc40 has more regressions on
a "make check-sid", than when compiled with 34. Could a cgen savvy person
take a look?
Meanwhile, I'm back to using 3.4.
Thanks.
next prev parent reply other threads:[~2005-07-01 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050630172848.GA4491@redhat.com>
2005-06-30 20:21 ` Frank Ch. Eigler
2005-07-01 10:45 ` Aldy Hernandez [this message]
2005-07-04 15:02 ` Frank Ch. Eigler
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=20050701104534.GA25446@redhat.com \
--to=aldyh@redhat.com \
--cc=fche@redhat.com \
--cc=jason@redhat.com \
--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).