* Re: [E2fsprogs] Compile error on RHEL4/ia64
[not found] <1217095878.3293.22.camel@alpha.linsyssoft.com>
@ 2008-07-26 18:22 ` Girish Shilamkar
2008-07-27 11:00 ` Theodore Tso
1 sibling, 0 replies; 2+ messages in thread
From: Girish Shilamkar @ 2008-07-26 18:22 UTC (permalink / raw)
To: Ext4 Mailing List
CC to mailing list also ...
On Sat, 2008-07-26 at 23:41 +0530, Girish Shilamkar wrote:
> Hi Ted,
> While building e2fsprogs on ia64/rhel4 the following compile error was
> flagged:
>
> Error messages:
> make[4]: Leaving directory `/cache/build/BUILD/e2fsprogs-1.40.7.sun1/lib/uuid'
> CC clear.c
> CC compare.c
> CC copy.c
> CC gen_uuid.c
> gen_uuid.c: In function `uuid__generate_time':
> gen_uuid.c:493: internal compiler error: in ia64_expand_load_address, at
> config/ia64/ia64.c:1184
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
> Preprocessed source stored into /tmp/ccYkSBN6.out file, please attach this to
> your bugreport.
> make[3]: *** [gen_uuid.o] Error 1
>
> e2fsprogs, if supported, sets TLS to appropriate TLS type, which happens to be
> '__thread' for Linux. And hence THREAD_LOCAL is defined as 'static __thread' in
> uuid_gen.c. But it seems that RHEL4 glibc is incompatible with TLS on ia64,
> though e2fsprogs detected that '__thread' is usable.
>
> Further investigation revealed that, With '-O' option it is ok on all
> (rhel4, rhel5, sles9 & sles10) distros but with optimization
> level >=2(-O2, -O3, ...) the problem occurs on RHEL4.
>
> https://bugzilla.lustre.org/show_bug.cgi?id=15514
> has more details about the tests run to verify the above findings,
> comments # 9 and 10.
>
> Regards,
> Girish
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [E2fsprogs] Compile error on RHEL4/ia64
[not found] <1217095878.3293.22.camel@alpha.linsyssoft.com>
2008-07-26 18:22 ` [E2fsprogs] Compile error on RHEL4/ia64 Girish Shilamkar
@ 2008-07-27 11:00 ` Theodore Tso
1 sibling, 0 replies; 2+ messages in thread
From: Theodore Tso @ 2008-07-27 11:00 UTC (permalink / raw)
To: Girish Shilamkar; +Cc: Andreas Dilger, Ext4 Mailing List
On Sat, Jul 26, 2008 at 11:41:18PM +0530, Girish Shilamkar wrote:
> Hi Ted,
> While building e2fsprogs on ia64/rhel4 the following compile error was
> flagged:
>
> Error messages:
> make[4]: Leaving directory `/cache/build/BUILD/e2fsprogs-1.40.7.sun1/lib/uuid'
> CC clear.c
> CC compare.c
> CC copy.c
> CC gen_uuid.c
> gen_uuid.c: In function `uuid__generate_time':
> gen_uuid.c:493: internal compiler error: in ia64_expand_load_address, at
> config/ia64/ia64.c:1184
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
> Preprocessed source stored into /tmp/ccYkSBN6.out file, please attach this to
> your bugreport.
> make[3]: *** [gen_uuid.o] Error 1
Well, as stated above, this is very clearly an IA64 optimizer bug in
GCC where it's not able to handle __thread with a pretty specific
piece of code.
It's also on a relatively ancient distribution and GCC version. You
could try reportig the bug to Red Hat to see if they are willing to
provide a fix. Failing that, probably the best thing to do is just to
use configure --disable-tls on a RHEL4/ia64 system. The main purpose
of the use of thread local storage is to avoid duplicate UUID's on SMP
systems when you have multiple threads generating UUID's at a very
high rate.
Certain database-driven applications will have a problem here, but
it's not clear it will matter for most users of Lustre.
Regards,
- Ted
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-07-27 11:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1217095878.3293.22.camel@alpha.linsyssoft.com>
2008-07-26 18:22 ` [E2fsprogs] Compile error on RHEL4/ia64 Girish Shilamkar
2008-07-27 11:00 ` Theodore Tso
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 NNTP newsgroup(s).