public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zack at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/6123] __pic__/__PIC__ not defined when -fpic/-fPIC is specified
Date: Mon, 08 Nov 2004 20:35:00 -0000	[thread overview]
Message-ID: <20041108203459.20197.qmail@sourceware.org> (raw)
In-Reply-To: <20020401103600.6123.ghazi@caip.rutgers.edu>



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |18382


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


  parent reply	other threads:[~2004-11-08 20:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020401103600.6123.ghazi@caip.rutgers.edu>
2003-06-05  3:37 ` [Bug middle-end/6123] sparc-sun-solaris2.7 gcc-3.1 C testsuite failure in verify_local_live_at_start w/-fpic|-fPIC on gcc.dg/20020312-2.c dhazeghi@yahoo.com
2003-06-09  5:57 ` ghazi@gcc.gnu.org
2004-07-10 20:00 ` [Bug middle-end/6123] __pic__/__PIC__ not defined when -fpic/-fPIC is specified ebotcazou at gcc dot gnu dot org
2004-10-09  0:31 ` [Bug target/6123] " pinskia at gcc dot gnu dot org
2004-11-08 20:35 ` zack at gcc dot gnu dot org [this message]
2004-11-08 20:37 ` zack at gcc dot gnu dot org
2004-11-08 20:45 ` kghazi at verizon dot net
2004-11-08 21:24 ` zack at codesourcery dot com
2004-11-10  5:07 ` amodra at bigpond dot net dot au
2004-11-10  5:13 ` amodra at bigpond dot net dot au
2004-11-16 22:42 ` cvs-commit at gcc dot gnu dot org
2005-01-03 21:03 ` ebotcazou 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=20041108203459.20197.qmail@sourceware.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).