public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/8947: Please add a Warning about "-malign-double" in docs
Date: Sat, 04 Jan 2003 02:36:00 -0000	[thread overview]
Message-ID: <20030104023603.26435.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/8947; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc-gnats@gcc.gnu.org, norbert_wolff@t-online.de
Subject: Re: other/8947: Please add a Warning about "-malign-double" in docs
Date: Fri, 3 Jan 2003 21:27:13 -0500

 On Fri, Jan 03, 2003 at 03:55:05PM -0800, Janis Johnson wrote:
 > The mainline version of install.texi includes the following
 > after the description of -malign-double:
 > 
 >   @strong{Warning:} if you use the @samp{-malign-double}
 >   switch, structures containing the above types will be
 >   aligned differently than the published application binary
 >   interface specifications for the 386.
 > 
 > If that's not strong enough, we could also add:
 > 
 >   Code compiled with @option{-malign-double} is not binary
 >   compatible with code compiled without that switch.
 > 
 > Similar language is now used for warnings about several
 > other options.
 
 I think that your proposed addition is exactly what we should say about
 this; it's much clearer to the layperson.
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2003-01-04  2:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04  2:36 Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-08  1:25 janis
2003-01-03 23:56 Janis Johnson
2003-01-03 23:26 Wolfgang Bangerth
2002-12-21  9:40 bangerth

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=20030104023603.26435.qmail@sources.redhat.com \
    --to=drow@mvista.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).