From: Michael Meissner <meissner@cygnus.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: Alias code
Date: Mon, 29 Jun 1998 19:43:00 -0000 [thread overview]
Message-ID: <199806291940.PAA03093@tiktok.cygnus.com> (raw)
| We've got a little problem.
|
| While the machine independent code is mostly free of gen_rtx (MEM)
| calls, many of the target files, and some of the front-ends that we
| want to interoperate (but possibly do not control) with are not free
| of such calls.
|
| I think we need to handle these cases in a clean manner. ie, we
| have to initialize the alias set field when we allocate the MEM or
| REG expression
We could always have the generic gen_rtx complain when it builds a MEM,
possibly under flag/ifdef control.
| Thoughts?
|
| jeff
|
| ps. i just spent 3hrs tracking down a case where the compiler would
| mis-compile a testcase, but not if you turned on -g or certain debug
| dumps -- it was tracked down to a call to gen_rtx (MEM) in a target
| config file. I don't want to have to do this very often :(
|
|
|
|
next reply other threads:[~1998-06-29 19:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-29 19:43 Michael Meissner [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-06-30 19:49 Mike Stump
1998-07-01 0:54 ` Jeffrey A Law
1998-06-29 22:34 Franz Sirl
1998-06-30 11:53 ` David Edelsohn
[not found] <199806291730.KAA16121@cygnus.com>
1998-06-29 20:41 ` Jeffrey A Law
1998-06-30 4:50 ` Michael P. Hayes
1998-06-30 14:46 ` Joern Rennecke
1998-07-01 0:54 ` Michael P. Hayes
1998-06-29 3:22 Jeffrey A Law
1998-06-29 11:08 ` Mark Mitchell
1998-06-29 22:34 ` Jeffrey A Law
1998-06-29 11:08 ` Mark Mitchell
1998-06-29 19:43 ` Jeffrey A Law
1998-06-29 14:05 ` Franz Sirl
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=199806291940.PAA03093@tiktok.cygnus.com \
--to=meissner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.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).