public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12382] New: [3.4 regression] targhooks.c:68: error: `asm_out_file' undeclared
Date: Tue, 23 Sep 2003 22:50:00 -0000	[thread overview]
Message-ID: <20030923221850.12382.danglin@gcc.gnu.org> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12382

           Summary: [3.4 regression] targhooks.c:68: error: `asm_out_file'
                    undeclared
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: danglin at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: hppa-unknown-linux-gnu
  GCC host triplet: hppa-unknown-linux-gnu
GCC target triplet: hppa-unknown-linux-gnu

gcc -c   -g  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-p
rototypes -pedantic -Wno-long-long -fno-common   -DHAVE_CONFIG_H    -I. -I. -I..
/../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include  ../../gcc/gcc/targhook
s.c -o targhooks.o
../../gcc/gcc/targhooks.c: In function `default_external_libcall':
../../gcc/gcc/targhooks.c:68: error: `asm_out_file' undeclared (first use in thi
s function)
../../gcc/gcc/targhooks.c:68: error: (Each undeclared identifier is reported onl
y once
../../gcc/gcc/targhooks.c:68: error: for each function it appears in.)


             reply	other threads:[~2003-09-23 22:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 22:50 danglin at gcc dot gnu dot org [this message]
2003-09-24  1:49 ` [Bug c/12382] " pinskia at gcc dot gnu dot org
2003-10-17 18:15 ` pinskia at gcc dot gnu dot org

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=20030923221850.12382.danglin@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).