[Python-Dev] ANSI strict aliasing and Python
Sat, 19 Jul 2003 20:25:56 +1000 (EST)
On Fri, 18 Jul 2003, Tim Peters wrote:
> [Andrew MacIntyre]
> > code; with gcc 3.2.1 I see 3 tests (test_codeccallbacks, test_format &
> > test_unicode) that seem to have repeatable failures that are
> > sensitive to optimisation level (-O3 = fail, -O2 = pass) which may be
> > bad code. I'll try -no-stict-aliasing when I get back digging into
> > this.
> It could also be plain bad code <wink>.
Not impossible... ;-) I'm mindful that gcc 3.x seems to create larger
stackframes than earlier versions, which has been a source of annoyance
(on FreeBSD more than with EMX).
> > BTW, the following sequence of tests causes a core dump from an
> > assertion failure in test_enumerate on EMX which I haven't been able
> > to replicate on FreeBSD :-(
> > test_importhooks
> > test_re
> > test_glob
> > test_parser
> > test_enumerate
> Excellent! I just reproduced this in a debug build on Win98SE.
I'm glad that I'm not alone in the wilderness on this one.
> We had a report on a Zope list today that 2.3b1 on FreeBSD (don't know more
> about the version) couldn't import fcntl. Doesn't sound like you've bumped
> into that one.
I did hit it, after I got a FreeBSD 5.1 box running to test on. The issue
is specific to FreeBSD 5.x. Patch 763798 was the fix, but wasn't checked
in until after 2.3b2.
Andrew I MacIntyre "These thoughts are mine alone..."
E-mail: firstname.lastname@example.org (pref) | Snail: PO Box 370
email@example.com (alt) | Belconnen ACT 2616
Web: http://www.andymac.org/ | Australia