From: Andries.Brouwer@cwi.nl
To: alan@lxorguk.ukuu.org.uk, bernds@redhat.com,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: gcc 2.95.2 is buggy
Date: Fri, 24 Nov 2000 02:57:45 +0100 (MET) [thread overview]
Message-ID: <UTC200011240157.CAA140709.aeb@aak.cwi.nl> (raw)
Yesterday night I wrote
> Note: this is not yet a confirmed compiler bug
but in the meantime there is good confirmation.
This really is a bug in gcc 2.95.2.
>From bernds@redhat.com Thu Nov 23 10:45:07 2000
> Please, could you send me ...
>From torvalds@transmeta.com Thu Nov 23 18:00:48 2000
> Can we get a show of hands?
Below a demo program.
Andries
-------------------- bug.c -----------------------------
/*
* bug.c - aeb, 001124
*
* This program shows a bug in gcc 2.95.2.
* It should print 0x0 and exit.
* For me it prints 0x84800000.
*
* Compile with:
* gcc -Wall -O2 -o bug bug.c
*/
#include <stdio.h>
struct inode {
long long i_size;
struct super_block *i_sb;
};
struct file {
long long f_pos;
};
struct super_block {
int s_blocksize;
unsigned char s_blocksize_bits;
int s_hs;
};
static char *
isofs_bread(unsigned int block)
{
printf("0x%x\n", block);
exit(0);
}
static int
do_isofs_readdir(struct inode *inode, struct file *filp)
{
int bufsize = inode->i_sb->s_blocksize;
unsigned char bufbits = inode->i_sb->s_blocksize_bits;
unsigned int block, offset;
char *bh = NULL;
int hs;
if (filp->f_pos >= inode->i_size)
return 0;
offset = filp->f_pos & (bufsize - 1);
block = filp->f_pos >> bufbits;
hs = inode->i_sb->s_hs;
while (filp->f_pos < inode->i_size) {
if (!bh)
bh = isofs_bread(block);
hs += block << bufbits;
if (hs == 0)
filp->f_pos++;
if (offset >= bufsize)
offset &= bufsize - 1;
if (*bh)
filp->f_pos++;
filp->f_pos++;
}
return 0;
}
struct super_block s;
struct inode i;
struct file f;
int
main(int argc, char **argv){
s.s_blocksize = 512;
s.s_blocksize_bits = 9;
i.i_size = 2048;
i.i_sb = &s;
f.f_pos = 0;
do_isofs_readdir(&i,&f);
return 0;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-24 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 1:57 Andries.Brouwer [this message]
2000-11-24 4:10 ` gcc 2.95.2 is buggy Chris Wedgwood
2000-11-24 6:10 ` Peter Samuelson
2000-11-24 8:27 ` kumon
2000-11-24 4:34 ` Gregory Maxwell
2000-11-24 4:47 ` Alexander Viro
2000-11-24 15:23 ` Tom Rini
2000-11-24 15:41 ` Bernd Schmidt
2000-11-26 16:09 ` Alessandro Suardi
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=UTC200011240157.CAA140709.aeb@aak.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bernds@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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