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: c/6300: [PATCH] sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c Date: Mon, 22 Apr 2002 14:46:00 -0000 [thread overview] Message-ID: <20020422214603.27661.qmail@sources.redhat.com> (raw) The following reply was made to PR c/6300; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.demon.co.uk> Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: c/6300: [PATCH] sparcv9-sun-solaris2.7 gcc-3.1 C testsuite failure in gcc.dg/cpp/charconst.c Date: Mon, 22 Apr 2002 14:43:11 -0700 On Mon, Apr 22, 2002 at 06:04:39PM +0100, Neil Booth wrote: > > I meant using precision based on the target, not the host. Oh, right. We could now do the "mask to correct size" trick; I don't have any better ideas short of a real arbitrary-precision library (which we need eventually but I'm not going there just now). > Do you have any ideas about handling target-dependence in cpplib? > > Whatever we do, I hope we can contain it to a single, probably new, > file. I believe we ought to be able to do most of it by adding entries to the options structure, which are set by cc1 during initialization. GDB needn't bother initializing them, since it only needs the macro expander, and it will have the target-dependent macro values right there in the debug information. zw
next reply other threads:[~2002-04-22 21:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-22 14:46 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-22 12:46 Kaveh R. Ghazi 2002-04-22 10:06 Neil Booth 2002-04-22 0:36 Zack Weinberg 2002-04-22 0:26 Zack Weinberg 2002-04-21 23:56 Neil Booth 2002-04-21 18:26 Zack Weinberg
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=20020422214603.27661.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: linkBe 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).