public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pbrook at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/17675] [Regression w.r.t. g77] Alignment constraints not honored in EQUIVALENCE
Date: Tue, 04 Jan 2005 22:48:00 -0000 [thread overview]
Message-ID: <20050104224824.11652.qmail@sourceware.org> (raw)
In-Reply-To: <20040926064644.17675.ebotcazou@gcc.gnu.org>
------- Additional Comments From pbrook at gcc dot gnu dot org 2005-01-04 22:48 -------
I don't think that patch is sufficient. I'm about halfway to a fix.
I don't think the behaviour should be conditional on STRICT_ALIGNMENT.
Either enforce alignment, or annotate things properly so that the backend
generates unaligned loads. g77 enforces alignment.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |pbrook at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
Last reconfirmed|2004-11-17 15:09:20 |2005-01-04 22:48:21
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17675
next prev parent reply other threads:[~2005-01-04 22:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 6:46 [Bug fortran/17675] New: " ebotcazou at gcc dot gnu dot org
2004-10-11 8:05 ` [Bug fortran/17675] " c dot christian dot joensson at comhem dot se
2004-11-13 14:32 ` [Bug fortran/17675] [4.0 Regression] " giovannibajo at libero dot it
2004-11-16 8:37 ` ebotcazou at gcc dot gnu dot org
2004-11-17 15:09 ` phython at gcc dot gnu dot org
2004-11-30 18:25 ` c dot christian dot joensson at comhem dot se
2004-12-17 20:42 ` [Bug fortran/17675] [Regression w.r.t. g77] " phython at gcc dot gnu dot org
2004-12-19 18:09 ` phython at gcc dot gnu dot org
2004-12-21 0:39 ` pinskia at gcc dot gnu dot org
2005-01-04 22:48 ` pbrook at gcc dot gnu dot org [this message]
2005-01-06 14:41 ` tobi at gcc dot gnu dot org
2005-01-08 21:43 ` pinskia at gcc dot gnu dot org
2005-01-09 22:58 ` cvs-commit at gcc dot gnu dot org
2005-01-09 22:59 ` pbrook at gcc dot gnu dot org
2005-01-09 23:16 ` ebotcazou at gcc dot gnu dot org
2005-01-16 12:06 ` cvs-commit at gcc dot gnu dot org
2005-01-16 15:48 ` ebotcazou at gcc dot gnu dot org
2005-01-16 16:08 ` pinskia at gcc dot gnu dot org
2005-01-16 16:13 ` dave at hiauly1 dot hia dot nrc dot ca
2005-01-16 23:17 ` dave at hiauly1 dot hia dot nrc dot ca
2005-01-16 23:21 ` pbrook 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=20050104224824.11652.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).