From: Zack Weinberg <zack@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Compiling GCC with g++: a report
Date: Wed, 25 May 2005 00:55:00 -0000 [thread overview]
Message-ID: <1116981782.8895.4.camel@localhost.localdomain> (raw)
In-Reply-To: <200505250027.j4P0Rb0t010519@greed.delorie.com>
On Tue, 2005-05-24 at 20:27 -0400, DJ Delorie wrote:
> > This is still not an answer to the question I originally asked - do you
> > see any way IN C to write code which has the relevant property of the
> > class above (that is, that the FOOmode constants are not accessible
> > except to authorized code) and which does not rely on free conversion
> > between enumeration constants and integral types?
>
> enum {
> TVQ_BAR_GRILL = (DATESTAMP % 10),
> TVQ_NEXT2,
> TVQ_NEXT3,
> TVQ_NEXT4
> } TheValQuux;
>
> It's evil, but it will keep programmers from hard-coding integer
> constants anywhere. The "constants" will need to be different every
> day.
This doesn't do what I want at all. The goal is to make the *symbolic
enumeration constants* inaccessible to most code.
Think about how machine_mode values are used. Almost the entire
compiler is supposed to treat them as opaque things. You get them from
e.g. int_mode_for_size; you may iterate over a class with
GET_MODE_WIDER_MODE; you stash them in RTL and you pass them to
predicates. Appearances of "SImode" in the machine-independent compiler
are usually bugs. This is a major contributing factor to the brokenness
of ports that don't set BITS_PER_UNIT==8.
The goal is to make "SImode" and its friends inaccessible in the
machine-independent compiler, so that that category of bugs cannot
arise.
zw
next prev parent reply other threads:[~2005-05-25 0:37 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 11:50 Gabriel Dos Reis
2005-05-23 12:22 ` Ranjit Mathew
2005-05-23 19:07 ` Tom Tromey
2005-05-23 18:04 ` Gabriel Dos Reis
2005-05-24 4:57 ` Gabriel Dos Reis
2005-05-24 4:59 ` Joseph S. Myers
2005-05-24 21:50 ` Kevin Handy
2005-05-25 12:02 ` Bernardo Innocenti
2005-05-24 5:54 ` Zack Weinberg
2005-05-24 6:04 ` Daniel Jacobowitz
2005-05-24 6:22 ` Gabriel Dos Reis
2005-05-24 6:29 ` Zack Weinberg
2005-05-24 6:31 ` Mark Mitchell
2005-05-24 7:08 ` Zack Weinberg
2005-05-24 7:09 ` Mark Mitchell
2005-05-24 7:39 ` Gabriel Dos Reis
2005-05-24 8:48 ` Zack Weinberg
2005-05-24 13:41 ` Gabriel Dos Reis
2005-05-25 0:47 ` Russ Allbery
2005-05-25 1:24 ` Gabriel Dos Reis
2005-05-24 16:07 ` Paolo Bonzini
2005-05-24 16:44 ` Daniel Jacobowitz
2005-05-24 23:53 ` Zack Weinberg
2005-05-25 0:06 ` Daniel Jacobowitz
2005-05-25 0:11 ` Richard Henderson
2005-05-25 0:22 ` Zack Weinberg
2005-05-25 0:26 ` Paolo Carlini
2005-05-25 0:37 ` Zack Weinberg
2005-05-25 0:43 ` Daniel Jacobowitz
2005-05-25 0:48 ` Zack Weinberg
2005-05-25 1:02 ` Paolo Carlini
2005-05-25 3:14 ` Daniel Jacobowitz
2005-05-25 13:30 ` libstdc++ soname and versioning (was: Re: Compiling GCC...) Paolo Carlini
2005-05-25 13:45 ` Theodore Papadopoulo
2005-05-25 13:53 ` libstdc++ soname and versioning Paolo Carlini
2005-05-25 14:18 ` Theodore Papadopoulo
2005-05-25 14:51 ` Gabriel Dos Reis
2005-05-25 14:52 ` Paolo Carlini
2005-05-25 13:54 ` libstdc++ soname and versioning (was: Re: Compiling GCC...) Gabriel Dos Reis
2005-05-25 14:35 ` Theodore Papadopoulo
2005-05-25 16:18 ` Compiling GCC with g++: a report Jason Merrill
2005-05-25 12:44 ` Christoph Hellwig
2005-05-25 13:33 ` Florian Weimer
2005-05-27 3:10 ` Marcin Dalecki
2005-05-24 6:13 ` Andrew Pinski
2005-05-24 6:25 ` Gabriel Dos Reis
2005-05-27 4:04 ` Marcin Dalecki
2005-05-24 6:18 ` Gabriel Dos Reis
2005-05-24 6:43 ` Zack Weinberg
2005-05-24 7:04 ` Mark Mitchell
2005-05-24 8:00 ` Gabriel Dos Reis
2005-05-25 3:45 ` Kaveh R. Ghazi
2005-05-25 7:45 ` DJ Delorie
2005-05-25 8:36 ` Gabriel Dos Reis
2005-05-25 13:38 ` Kaveh R. Ghazi
2005-05-26 13:40 ` Gabriel Dos Reis
2005-05-24 7:38 ` Gabriel Dos Reis
2005-05-24 8:32 ` Zack Weinberg
2005-05-24 13:18 ` Gabriel Dos Reis
2005-05-24 23:45 ` Zack Weinberg
2005-05-25 0:29 ` Gabriel Dos Reis
2005-05-25 0:37 ` Zack Weinberg
2005-05-25 0:52 ` DJ Delorie
2005-05-25 0:55 ` Zack Weinberg [this message]
2005-05-25 1:02 ` Ian Lance Taylor
2005-05-25 1:36 ` DJ Delorie
2005-05-25 1:40 ` Zack Weinberg
2005-05-25 2:24 ` Gabriel Dos Reis
2005-05-25 21:37 ` hidden enum constants (Was: Compiling GCC with g++: a report) Giovanni Bajo
2005-05-25 1:50 ` Compiling GCC with g++: a report Gabriel Dos Reis
2005-05-25 2:20 ` DJ Delorie
2005-05-25 1:47 ` Gabriel Dos Reis
2005-05-25 2:08 ` DJ Delorie
2005-05-25 2:36 ` Gabriel Dos Reis
2005-05-25 3:34 ` DJ Delorie
2005-05-25 5:01 ` Gabriel Dos Reis
2005-05-25 1:12 ` Gabriel Dos Reis
2005-05-25 1:47 ` DJ Delorie
2005-05-25 3:20 ` Gabriel Dos Reis
2005-05-27 1:20 ` Marcin Dalecki
2005-05-24 17:17 ` Paul Koning
2005-05-24 17:25 ` Andreas Schwab
2005-05-24 20:43 ` Joe Buck
2005-05-24 21:40 ` Dale Johannesen
2005-05-24 17:49 ` Gabriel Dos Reis
2005-05-24 6:26 ` Mark Mitchell
2005-05-24 6:54 ` Zack Weinberg
2005-05-24 7:04 ` Mark Mitchell
2005-05-24 15:03 ` Kai Henningsen
2005-05-25 9:51 ` Jason Merrill
2005-05-24 10:01 ` Florian Weimer
2005-05-24 14:22 ` Gabriel Dos Reis
2005-05-24 18:00 ` Diego Novillo
2005-05-24 20:41 ` Richard Guenther
2005-05-24 23:14 ` Kevin Handy
2005-05-27 3:47 ` Marcin Dalecki
2005-05-27 1:20 ` Marcin Dalecki
2005-05-25 5:26 Paul Schlie
2005-05-25 6:10 ` DJ Delorie
2005-05-25 11:46 ` Paul Schlie
2005-05-25 18:31 ` DJ Delorie
2005-05-25 21:41 ` Paul Schlie
2005-05-26 6:11 ` DJ Delorie
2005-05-26 8:15 ` Paul Schlie
2005-05-26 11:57 ` DJ Delorie
2005-05-25 19:27 Richard Kenner
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=1116981782.8895.4.camel@localhost.localdomain \
--to=zack@codesourcery.com \
--cc=dj@redhat.com \
--cc=gcc@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).