public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@anchor.cs.utah.edu>
To: Richard Henderson <rth@cygnus.com>
Cc: Donn Terry <donn@interix.com>,
	"egcs@egcs.cygnus.com" <egcs@egcs.cygnus.com>
Subject: Re: ISO C violation (really -- style & string pasting)
Date: Thu, 25 Mar 1999 15:36:00 -0000	[thread overview]
Message-ID: <6682.922404936@anchor.cs.utah.edu> (raw)
In-Reply-To: <19990325142948.E27147@cygnus.com>

  In message < 19990325142948.E27147@cygnus.com >you write:
  > On Wed, Mar 24, 1999 at 05:34:18PM -0700, Donn Terry wrote:
  > > The easy fix to this is to use a #define and (ISO) string-pasting.
  > > However, I suspect the style rules disallow string-pasting.
  > > (If they don't, then we're done, and I'm home free.)
  > 
  > No.  Just create a GLOBAL_OFFSET_TABLE_SYMBOL define to use
  > within i386.{h,c,md} instead of the current string literal.
  > You can then override this for coff or whatever as needed.
This is what I recommended too.

jeff

WARNING: multiple messages have this Message-ID

From: Jeffrey A Law <law@anchor.cs.utah.edu>
To: Richard Henderson <rth@cygnus.com>
Cc: Donn Terry <donn@interix.com>,
	"egcs@egcs.cygnus.com" <egcs@egcs.cygnus.com>
Subject: Re: ISO C violation (really -- style & string pasting)
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <6682.922404936@anchor.cs.utah.edu> (raw)
Message-ID: <19990331234600.WROglFJVL4M8t5nOOCaQXUWjMrwzLK6_qkBYG3uvwck@z> (raw)
In-Reply-To: <19990325142948.E27147@cygnus.com>

  In message < 19990325142948.E27147@cygnus.com >you write:
  > On Wed, Mar 24, 1999 at 05:34:18PM -0700, Donn Terry wrote:
  > > The easy fix to this is to use a #define and (ISO) string-pasting.
  > > However, I suspect the style rules disallow string-pasting.
  > > (If they don't, then we're done, and I'm home free.)
  > 
  > No.  Just create a GLOBAL_OFFSET_TABLE_SYMBOL define to use
  > within i386.{h,c,md} instead of the current string literal.
  > You can then override this for coff or whatever as needed.
This is what I recommended too.

jeff

  parent reply	other threads:[~1999-03-25 15:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-24 16:38 Donn Terry
     [not found] ` < 36F9848A.9F566D1A@interix.com >
1999-03-24 23:35   ` Martin v. Loewis
1999-03-25  8:09     ` Donn Terry
     [not found]       ` < 36FA5EC7.3144D054@interix.com >
1999-03-25 14:26         ` Martin v. Loewis
1999-03-25 15:05           ` Donn Terry
1999-03-25 15:31             ` Martin v. Loewis
1999-03-31 23:46               ` Martin v. Loewis
1999-03-31 23:46             ` Donn Terry
1999-03-31 23:46           ` Martin v. Loewis
1999-03-31 23:46       ` Donn Terry
1999-03-31 23:46     ` Martin v. Loewis
1999-03-25 14:29   ` Richard Henderson
1999-03-25 14:51     ` Donn Terry
1999-03-25 15:07       ` Richard Henderson
1999-03-25 15:25         ` Donn Terry
1999-03-25 15:39           ` Jeffrey A Law
1999-03-31 23:46             ` Jeffrey A Law
1999-03-31 23:46           ` Donn Terry
1999-03-31 23:46         ` Richard Henderson
1999-03-31 23:46       ` Donn Terry
1999-03-25 15:14     ` espie
1999-03-25 15:35       ` Donn Terry
1999-03-31 23:46         ` Donn Terry
1999-03-31 23:46       ` espie
1999-03-25 15:36     ` Jeffrey A Law [this message]
1999-03-31 23:46       ` Jeffrey A Law
1999-03-31 23:46     ` Richard Henderson
1999-03-31 23:46 ` Donn Terry

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=6682.922404936@anchor.cs.utah.edu \
    --to=law@anchor.cs.utah.edu \
    --cc=donn@interix.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=rth@cygnus.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).