public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o file
Date: Sun, 29 Apr 2001 05:46:00 -0000	[thread overview]
Message-ID: <20010429124601.32074.qmail@sourceware.cygnus.com> (raw)

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

From: Phil Edwards <pedwards@disaster.jaj.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o file
Date: Sun, 29 Apr 2001 07:20:29 -0400

 On Sun, Apr 29, 2001 at 01:26:53PM +0100, Joseph S. Myers wrote:
 > On 29 Apr 2001, Phil Edwards wrote:
 > >  I think that's .ident, not .comment.  (Was ".command" a typo for ".comment"?)
 > 
 > .ident assembler directives put data in .comment.
 
 Duh... this is what happens when I post without sleep.
 
 
 > Since the original message mentioned both .comment and .command, I think
 > .command did mean .comment.
 
 Pity, a .command section would've been useful for this.
 
 
 -- 
 pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
 devphil at several other less interesting addresses in various dot domains
 The gods do not protect fools.  Fools are protected by more capable fools.


             reply	other threads:[~2001-04-29  5:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-29  5:46 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05  9:16 Wolfgang Bangerth
2002-11-05  9:08 bangerth
2002-11-05  9:06 Phil Edwards
2002-11-05  7:46 Wolfgang Bangerth
2001-05-07 16:56 Phil Edwards
2001-04-30 17:36 Ronald F. Guilmette
2001-04-30 17:16 Phil Edwards
2001-04-30 10:26 Ronald F. Guilmette
2001-04-30  9:46 Ronald F. Guilmette
2001-04-30  2:36 Phil Edwards
2001-04-30  2:16 Ronald F. Guilmette
2001-04-29 20:06 Phil Edwards
2001-04-29 11:56 Ronald F. Guilmette
2001-04-29  5:16 Phil Edwards
2001-04-29  4:16 Phil Edwards
2001-04-28 13:46 rfg

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=20010429124601.32074.qmail@sourceware.cygnus.com \
    --to=pedwards@disaster.jaj.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).