public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libgcj/5789: boehm-gc won't build on irix - irix assembler chokes on #indent
Date: Mon, 04 Mar 2002 08:36:00 -0000	[thread overview]
Message-ID: <20020304163602.10524.qmail@sources.redhat.com> (raw)

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

From: Zack Weinberg <zack@codesourcery.com>
To: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
Cc: java@gcc.gnu.org, hans_boehm@hp.com, gcc-gnats@gcc.gnu.org,
	gcc-bugs@gcc.gnu.org
Subject: Re: libgcj/5789: boehm-gc won't build on irix - irix assembler chokes on #indent
Date: Mon, 4 Mar 2002 08:26:22 -0800

 On Sat, Mar 02, 2002 at 09:53:54AM +0800, Billinghurst, David (CRTS) wrote:
 > Version:  3.1 and 3.2
 > System: mips-sgi-irix6.5
 > 
 > The problem
 > 
 > Error compiling boehm-gc/mips_sgi_mach_dep.S
 > 
 > as: Error: /usr/include/sys/regdef.h, line 17: Expected cpp-generated line number
 > as INTERNAL ERROR:  /usr/lib32/cmplrs/asm returned non-zero status 1
 > 
 > 
 > Cause
 > 
 > The Irix header files
 >   /usr/include/sys/regdef.h
 >   /usr/include/sgidefs.h
 >   /usr/include/sys/asm.h
 > contain #ident "$Revision: 3.52 $" lines.
 > 
 > The gcc cpp passess these through to the .s file, and the irix
 > assembler chokes on them.  
 
 Sounds like it's incorrect to emit #ident lines in CPP when we're
 processing assembly language.  That's not hard -- please try this
 patch.
 
 zw
 
 ===================================================================
 Index: cppmain.c
 --- cppmain.c	2002/01/03 21:43:06	1.90
 +++ cppmain.c	2002/03/04 16:25:37
 @@ -193,8 +193,13 @@ setup_callbacks ()
    if (! options->no_output)
      {
        cb->line_change = cb_line_change;
 -      cb->ident      = cb_ident;
 -      cb->def_pragma = cb_def_pragma;
 +      /* Don't emit #pragma or #ident directives if we are processing
 +	 assembly language; the assembler may choke on them.  */
 +      if (options->lang != CLK_ASM)
 +	{
 +	  cb->ident      = cb_ident;
 +	  cb->def_pragma = cb_def_pragma;
 +	}
        if (! options->no_line_commands)
  	cb->file_change = cb_file_change;
      }


             reply	other threads:[~2002-03-04 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-04  8:36 Zack Weinberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-04 15:36 Zack Weinberg
2002-03-04 15:16 Billinghurst, David (CRTS)
2002-03-04 12:26 Neil Booth
2002-03-03 23:46 Bryce McKinlay
2002-03-01 22:46 Billinghurst, David (CRTS)

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=20020304163602.10524.qmail@sources.redhat.com \
    --to=zack@codesourcery.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).