public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/5899: -M disables -dM
Date: Sat, 09 Mar 2002 12:56:00 -0000	[thread overview]
Message-ID: <20020309205601.25649.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

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

From: Andreas Schwab <schwab@suse.de>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/5899: -M disables -dM
Date: Sat, 09 Mar 2002 21:50:56 +0100

 Neil Booth <neil@daikokuya.demon.co.uk> writes:
 
 |> Andreas Schwab wrote:-
 |> 
 |> > IMHO neither -dM nor -M produce "normal output", so it would not
 |> > contradict the docs to output both.
 |> 
 |> Sure, but it wasn't mentioned that it outputs to two streams
 |> simultaneously.  2.95 didn't.
 |> 
 |> > Both 2.95 and 3.0.4 behave as expected by glibc.
 |> 
 |> What is "expected by glibc"?  It's not what you posted, since 2.95.4
 |> didn't support -MF.
 
 glibc uses the equivalent functionality provided by SUNPRO_DEPENDENCIES:
 
 # Generate the list of SYS_* macros for the system calls (__NR_* macros).
 $(objpfx)syscall-%.h $(objpfx)syscall-%.d: ../sysdeps/unix/sysv/linux/sys/syscall.h
 	rm -f $(@:.h=.d)-t
 	{ \
 	 echo '/* Generated at libc build time from kernel syscall list.  */';\
 	 echo ''; \
 	 echo '#ifndef _SYSCALL_H'; \
 	 echo '# error "Never use <bits/syscall.h> directly; include <sys/syscall.h> instead."'; \
 	 echo '#endif'; \
 	 echo ''; \
 	 SUNPRO_DEPENDENCIES='$(@:.h=.d)-t $@' \
 	 $(CC) -E -x c $(sysincludes) $< -D_LIBC -dM | \
 	 sed -n 's@^#define __NR_\([^ ]*\) .*$$@#define SYS_\1 __NR_\1@p'; \
 	} > $(@:.d=.h).new
 	mv -f $(@:.d=.h).new $(@:.d=.h)
 	sed < $(@:.h=.d)-t > $(@:.h=.d)-t2 \
 	    -e 's,$(subst .,\.,$@),$(patsubst $(objpfx)%,$$(objpfx)%,\
 					      $(@:.d=.h) $(@:.h=.d)),'
 	rm -f $(@:.h=.d)-t
 	mv -f $(@:.h=.d)-t2 $(@:.h=.d)
 
 Andreas.
 
 -- 
 Andreas Schwab, SuSE Labs, schwab@suse.de
 SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
 Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
 "And now for something completely different."


             reply	other threads:[~2002-03-09 20:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 12:56 Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-10 13:54 neil
2002-03-09 13:16 Andreas Schwab
2002-03-09 13:16 Neil Booth
2002-03-09 12:56 Neil Booth
2002-03-09 11:56 Andreas Schwab
2002-03-09 11:40 neil
2002-03-09 10:26 schwab

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=20020309205601.25649.qmail@sources.redhat.com \
    --to=schwab@suse.de \
    --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).