public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: Kristis Makris <kristis.makris@asu.edu>
Cc: Zack Weinberg <zack@codesourcery.com>, gcc-bugs@gcc.gnu.org
Subject: Re: noreturn function attribute and ret asm instruction
Date: Sat, 13 Sep 2003 03:41:00 -0000 [thread overview]
Message-ID: <1063416307.1007.15.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <1063386860.3208.7.camel@syd.monet.net>
On Fri, 2003-09-12 at 10:14, Kristis Makris wrote:
> Here %eax is used and it's previous value is not preserved. Again
> conceptually I should be able to write in a high-level language such as
> C with the option to tell gcc to preserve the registers it will end up
> using on its own.
You haven't given any justification for why you want this feature. We
aren't going to add features that have no known use. Maybe if you
explained what you are trying to do, we could offer a better
alternative, or give reasons why what you want to do won't work.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2003-09-13 1:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 16:33 Kristis Makris
2003-08-25 20:30 ` Jim Wilson
2003-08-26 6:51 ` Kristis Makris
2003-08-26 7:05 ` Zack Weinberg
2003-08-30 0:09 ` Kristis Makris
2003-09-02 21:17 ` Jim Wilson
2003-09-02 21:57 ` Zack Weinberg
2003-09-02 22:02 ` Joseph S. Myers
2003-09-03 2:19 ` Kristis Makris
2003-09-12 1:29 ` Kristis Makris
2003-09-12 7:10 ` Jim Wilson
2003-09-12 18:16 ` Kristis Makris
2003-09-13 3:41 ` Jim Wilson [this message]
2003-09-14 17:31 ` Kristis Makris
2003-09-14 20:22 ` Jim Wilson
2003-09-15 18:21 ` Kristis Makris
2003-09-15 20:15 ` Jim Wilson
2003-10-01 5:59 ` Hans-Peter Nilsson
2003-10-01 7:00 ` Zack Weinberg
2003-10-01 7:26 ` Hans-Peter Nilsson
2003-10-01 16:21 ` Richard Henderson
2003-10-01 17:57 ` Zack Weinberg
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=1063416307.1007.15.camel@leaf.tuliptree.org \
--to=wilson@tuliptree.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=kristis.makris@asu.edu \
--cc=zack@codesourcery.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).