From: Eric Christopher <echristo@redhat.com>
To: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
Cc: gcc-patches@gcc.gnu.org, uweigand@de.ibm.com
Subject: Re: [PATCH]
Date: Tue, 04 May 2004 00:52:00 -0000 [thread overview]
Message-ID: <1083631924.32152.53.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <200405040040.CAA06815@faui1d.informatik.uni-erlangen.de>
On Mon, 2004-05-03 at 17:40, Ulrich Weigand wrote:
> Eric Christoper wrote:
>
> >Having lots of problems with the tpf tracing functions until it was
> >realized that they don't actually affect anything and don't need
> >standard call mechanisms for save and restore either, just execute.
>
> How come? Your change shouldn't generate any different code;
> could you elaborate what the problems were?
Regrename wanted to start changing things around and inside the branch
and then flow would complain about register liveness later. Optimization
would also play havoc with varargs. I can send you a couple of testcases
if you'd like...
>
> >+(define_insn "prologue_tpf"
> >+ [(unspec_volatile [(const_int 0)] UNSPECV_TPF_PROLOGUE)]
> >+ "TARGET_TPF"
> >+ "bas\t%%r1,4064"
> >+ [(set_attr "type" "jsr")])
>
> We should have a (clobber (reg 1)) here at least ...
I thought that it wouldn't be guaranteed to have anything there going in
here, but I can add the clobber.
-eric
--
Eric Christopher <echristo@redhat.com>
next prev parent reply other threads:[~2004-05-04 0:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 0:42 [PATCH] Ulrich Weigand
2004-05-04 0:52 ` Eric Christopher [this message]
2004-05-04 1:14 ` [PATCH] Ulrich Weigand
2004-05-04 2:05 ` [PATCH] Eric Christopher
2004-05-04 1:11 ` [PATCH] Eric Christopher
2004-05-04 1:14 ` [PATCH] Ulrich Weigand
[not found] <ormtqpsbuc.fsf@lxoliva.fsfla.org>
2021-09-09 7:11 ` [PATCH] strub: machine-independent stack scrubbing Alexandre Oliva
2022-07-29 6:16 ` [PATCH v2 00/10] Introduce " Alexandre Oliva
2023-06-16 6:09 ` [PATCH v3] " Alexandre Oliva
2023-10-20 6:03 ` [PATCH v4] " Alexandre Oliva
2023-10-26 6:15 ` Alexandre Oliva
2023-11-20 12:40 ` Alexandre Oliva
2023-11-22 14:14 ` Richard Biener
2023-11-23 10:56 ` Alexandre Oliva
2023-11-23 12:05 ` Richard Biener
2023-11-29 8:53 ` Alexandre Oliva
2023-11-29 12:48 ` Richard Biener
2023-11-30 4:13 ` Alexandre Oliva
2023-11-30 12:00 ` Richard Biener
2023-12-02 17:56 ` [PATCH v5] " Alexandre Oliva
2023-12-06 8:36 ` Causes to nvptx bootstrap fail: " Tobias Burnus
2023-12-06 11:32 ` Thomas Schwinge
2023-12-06 22:12 ` Alexandre Oliva
2023-12-07 3:33 ` [PATCH] strub: enable conditional support Alexandre Oliva
2023-12-07 16:44 ` Thomas Schwinge
2023-12-07 17:52 ` [PATCH] Alexandre Oliva
2023-12-08 6:46 ` [PATCH] Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2006-10-10 19:31 [PATCH]: Kaveh R. GHAZI
2006-05-10 10:44 [patch] François-Xavier Coudert
[not found] <no.id>
2004-05-04 0:50 ` [PATCH] Ulrich Weigand
2004-05-04 0:52 ` [PATCH] Eric Christopher
2004-05-04 0:26 [PATCH] Eric Christopher
2004-02-08 22:05 [PATCH] Bernardo Innocenti
2004-02-08 22:55 ` [PATCH] Richard Henderson
2004-02-21 13:45 ` [PATCH] Richard Henderson
2004-02-21 13:45 ` [PATCH] Bernardo Innocenti
2003-12-16 14:00 [PATCH] Hartmut Penner
2003-12-16 17:36 ` [PATCH] Zack Weinberg
2003-02-20 12:36 [PATCH] Zdenek Dvorak
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=1083631924.32152.53.camel@dzur.sfbay.redhat.com \
--to=echristo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=uweigand@de.ibm.com \
--cc=weigand@i1.informatik.uni-erlangen.de \
/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).