Bug 4423 – glibc-2.1.2-3: Expat in Mozilla won't compile with -O

Bug 4423 - glibc-2.1.2-3: Expat in Mozilla won't compile with -O

Summary:	glibc-2.1.2-3: Expat in Mozilla won't compile with -O

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	glibc (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Cristian Gafton
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-08-08 00:39 EDT by Brian Ryner
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-08-10 21:52:19 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Brian Ryner 1999-08-08 00:39:20 EDT

With glibc-2.1.2-3, expat in Mozilla chokes when trying to
compile with -O.  I haven't extensively analyzed it, but it
looks like it might be a problem with a macro definition of
memset().

This is with the current Mozilla code from CVS, configured
with --enable-optimize.

Comment 1 Brian Ryner 1999-08-08 02:19:59 EDT

I think my original guess that this is a memset() problem might be
wrong.  If you remove the line:

#define int int32

in expat/xmltok/xmldef.h, the problem goes away.  Of course this
doesn't guarantee a 32-bit integer, so it's not a real solution.

Comment 2 Brian Ryner 1999-08-09 16:07:59 EDT

A workaround is being checked in for mozilla.  However, we don't yet
know the real reason that the original code did not work, and why it
only breaks with -O.

Also, it is possible that this is an egcs problem.  I'm using
egcs-1.1.2-17 from Rawhide.

Comment 3 Cristian Gafton 1999-08-10 21:52:59 EDT

I am not sure where the problem is - please reopen the bug if you can
isolate the problem further.

Note You need to log in before you can comment on or make changes to this bug.