From: Brian Gough <bjg@network-theory.co.uk>
To: gsl-discuss@sources.redhat.com
Subject: Re: Problem building vector/reim_source.c
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15232.62389.804947.499891@debian> (raw)
In-Reply-To: <20010819085952.A86400@oolong.il.thewrittenword.com>
gsl-discuss@lists.thewrittenword.com writes:
> I've opened a problem report with Sun and gave them a small test case
> to reproduce the bug. I'll forward your info below if they need
> convincing.
Sounds good. You probably saw it on comp.std.c but just for reference
this was the simplest test case I could find:
----------------------------------------------------------------------
$ cat test.c
#include <stdio.h>
typedef struct {
int k;
const int kmax;
} A;
A create_A (void)
{
A a = { 1, 2 };
return a ;
}
int main (void)
{
A a = create_A ();
printf("a.k=%d\n", a.k);
printf("a.kmax=%d\n", a.kmax);
return 0;
}
$ gcc -ansi -pedantic -Wall -O2 test.c # gcc-2.7.2.3 and gcc-3.0
$ ./a.out
a.k=1
a.kmax=2
$ cc -V test.c
cc: Sun WorkShop 6 update 1 C 5.2 2000/09/11
acomp: Sun WorkShop 6 update 1 C 5.2 2000/09/11
"test.c", line 11: left operand must be modifiable lvalue: op "="
"test.c", line 16: left operand must be modifiable lvalue: op "="
cc: acomp failed for test.c
----------------------------------------------------------------------
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 gsl-discuss
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough [this message]
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
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=15232.62389.804947.499891@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
/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).