public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Kelley Cook <kcook@gcc.gnu.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	GCC Mailing List <gcc@gcc.gnu.org>,
	Bauke van Dijk <bauke.vandijk@planet.nl>,
	GCC Bugs <gcc-bugs@gcc.gnu.org>
Subject: Re: [PR bootstrap/14356] Error building 3.3.4 on i686-cygwin.
Date: Thu, 25 Mar 2004 05:41:00 -0000	[thread overview]
Message-ID: <m365ct7qdi.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <406209C0.1040601@ford.com>

Kelley Cook <kcook34@ford.com> writes:

|  > ../../gcc/gcc/gcc.c: In function `process_command':
|  > ../../gcc/gcc/gcc.c:3609: error: assignment of read-only location
|  > ../../gcc/gcc/gcc.c:3611: error: assignment of read-only location
|  > make[2]: *** [gcc.o] Error 1
| 
| I hadn't tried CVS GCC 3.3 in a while, but I suspect that Mark
| Mitchell's patch to better diagnose constness was backported to GCC
| 3.3, which exposed a latent bug in gcc.c when it was ported to
| mainline and 3.4.
| 
| This became PR 14356
| 
| Anyway that was solved by:
| http://gcc.gnu.org/ml/gcc-patches/2004-03/msg00120.html which I would
| think should also now be backported to the GCC 3.3 branch.
| 
| Gaby,
| 
| Would this be OK if it passes an overnight bootstrap on i686-pc-cygwin?
| It is different from Mark's patch as it had to be readjusted for K&R-ness.

Yes, you have been quicker than me at looking at this (though day here).
Please apply it.

Thanks,

-- Gaby

  reply	other threads:[~2004-03-25  0:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25  0:00 Bauke van Dijk
2004-03-25  1:07 ` [PR bootstrap/14356] " Kelley Cook
2004-03-25  5:41   ` Gabriel Dos Reis [this message]
2004-03-25 19:35   ` Bauke van Dijk

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=m365ct7qdi.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=bauke.vandijk@planet.nl \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kcook@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).