public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/17180] [3.4 Regression] nearly all g77 tests fail
Date: Thu, 02 Sep 2004 07:48:00 -0000 [thread overview]
Message-ID: <20040902074823.14727.qmail@sourceware.org> (raw)
In-Reply-To: <20040825065523.17180.debian-gcc@lists.debian.org>
------- Additional Comments From mark at codesourcery dot com 2004-09-02 07:48 -------
Subject: Re: [3.4 Regression] nearly all g77 tests fail
ebotcazou at gcc dot gnu dot org wrote:
>------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-09-02 06:08 -------
>I think the patch is not really correct because the pool is used on the host,
>not on the target. We probably need something like:
>
>struct max_alignment {
> char c;
> union {
> HOST_WIDEST_INT i;
>#ifdef HAVE_LONG_DOUBLE
> long double d;
>#else
> double d;
>#endif
> } u;
>
>#define MAX_ALIGNMENT (offsetof (struct max_alignment, u))
>
>
Yes, that makes sense to me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17180
next prev parent reply other threads:[~2004-09-02 7:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 6:55 [Bug target/17180] New: nearly all g77 tests fail on sparc-linux debian-gcc at lists dot debian dot org
2004-08-25 7:16 ` [Bug target/17180] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-08-29 19:09 ` mmitchel at gcc dot gnu dot org
2004-08-30 10:31 ` ebotcazou at gcc dot gnu dot org
2004-08-31 4:23 ` ebotcazou at gcc dot gnu dot org
2004-08-31 4:24 ` [Bug target/17180] [3.4 Regression] nearly all g77 tests fail ebotcazou at gcc dot gnu dot org
2004-08-31 5:00 ` ebotcazou at gcc dot gnu dot org
2004-08-31 5:11 ` mark at codesourcery dot com
2004-08-31 5:32 ` ebotcazou at gcc dot gnu dot org
2004-08-31 5:47 ` ebotcazou at gcc dot gnu dot org
2004-08-31 5:53 ` pinskia at gcc dot gnu dot org
2004-08-31 6:37 ` ebotcazou at gcc dot gnu dot org
2004-08-31 9:31 ` bdavis at gcc dot gnu dot org
2004-08-31 10:35 ` ebotcazou at gcc dot gnu dot org
2004-08-31 10:39 ` bdavis9659 at comcast dot net
2004-08-31 17:28 ` ebotcazou at gcc dot gnu dot org
2004-09-01 1:15 ` bdavis at gcc dot gnu dot org
2004-09-01 5:10 ` ebotcazou at gcc dot gnu dot org
2004-09-01 6:03 ` mmitchel at gcc dot gnu dot org
2004-09-01 7:23 ` [Bug fortran/17180] " cvs-commit at gcc dot gnu dot org
2004-09-01 7:25 ` ebotcazou at gcc dot gnu dot org
2004-09-01 10:20 ` ebotcazou at gcc dot gnu dot org
2004-09-02 6:08 ` ebotcazou at gcc dot gnu dot org
2004-09-02 7:48 ` mark at codesourcery dot com [this message]
2004-09-02 16:04 ` cvs-commit at gcc dot gnu dot org
2004-09-02 16:06 ` ebotcazou at gcc dot gnu dot org
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=20040902074823.14727.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).