public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sabre at nondot dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/31128] __builtin_stack_restore/__builtin_stack_save should not be exposed to the user
Date: Wed, 28 Nov 2007 20:57:00 -0000 [thread overview]
Message-ID: <20071128205722.6396.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31128-14221@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from sabre at nondot dot org 2007-11-28 20:57 -------
Please don't disable these. There are a variety of compilers that optionally
or only generate C code, particularly for the functional languages. This is
useful functionality for these compilers.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31128
next prev parent reply other threads:[~2007-11-28 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 1:46 [Bug c/31128] New: ICE with __builtin_stack_restore nicholas at mxc dot ca
2007-03-11 1:51 ` [Bug c/31128] " pinskia at gcc dot gnu dot org
2007-03-11 1:58 ` [Bug c/31128] __builtin_stack_restore/__builtin_stack_save should not be exposed to the user pinskia at gcc dot gnu dot org
2007-03-11 2:16 ` nicholas at mxc dot ca
2007-03-11 2:20 ` pinskia at gcc dot gnu dot org
2007-03-11 2:57 ` pinskia at gcc dot gnu dot org
2007-05-28 17:44 ` sabre at nondot dot org
2007-05-28 19:08 ` pinskia at gcc dot gnu dot org
2007-05-29 15:14 ` sabre at nondot dot org
2007-11-17 18:21 ` pinskia at gcc dot gnu dot org
2007-11-17 19:25 ` jakub at gcc dot gnu dot org
2007-11-28 20:57 ` sabre at nondot dot org [this message]
2007-12-04 22:02 ` jakub at gcc dot gnu dot org
2008-01-03 18:04 ` pinskia at gcc dot gnu dot org
2008-01-24 19:13 ` edmar at freescale dot com
[not found] <bug-31128-4@http.gcc.gnu.org/bugzilla/>
2024-04-02 6:55 ` pinskia at gcc dot gnu.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=20071128205722.6396.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).