public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: kuball@zedo.fuedo.de
Cc: egcs-bugs@cygnus.com
Subject: Re: egcs 1.1a on DEC alpha OSF/3.2, problem with include files
Date: Thu, 10 Sep 1998 07:15:00 -0000	[thread overview]
Message-ID: <or3ea0f3yi.fsf@rabico.lsd.dcc.unicamp.br> (raw)
In-Reply-To: <199809101102.NAA04310@zedo.fuedo.de>

kuball  <kuball@zedo.fuedo.de> writes:

> Where can I find an explanation of the structure of the temp files?

It is just the output of the preprocessor.  All macros and #includes
are expanded, and #ifs are resolved.  Lines starting with `#' indicate 
the line number and file their following lines come from.

> Looking at test.ii gives no answers, but new questions: there is no
> prototype for strcmp in the temp file, either. So why does the compiler
> warn about strncmp but not about strcmp???

Are you sure?  I haven't got access to an OSF/3.2 host, only to 4.0,
but strcmp shows up in the preprocessed output for me.  Does string.h
appear in the preprocessed output?  Is it read from the directory
where you expect it to live?

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil



  reply	other threads:[~1998-09-10  7:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-09  4:04 kuball
1998-09-09 23:49 ` Alexandre Oliva
1998-09-10  4:04   ` kuball
1998-09-10  7:15     ` Alexandre Oliva [this message]
     [not found] <199809110842.KAA09831@zedo.fuedo.de>
1998-09-11 22:38 ` Alexandre Oliva
1998-09-14  4:35   ` kuball
     [not found] <orr9xelie0.fsf@tiete.dcc.unicamp.br>
1998-09-14 13:55 ` Jeffrey A Law
1998-09-15 15:30   ` Alexandre Oliva
1998-09-15 15:39     ` Jeffrey A Law
1998-09-15 19:06       ` Alexandre Oliva
1998-09-16  1:43         ` Jeffrey A Law
1998-09-16  5:01       ` kuball

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=or3ea0f3yi.fsf@rabico.lsd.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=egcs-bugs@cygnus.com \
    --cc=kuball@zedo.fuedo.de \
    /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).