This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc4: missing atomic builtins?

Yaakov (Cygwin/X) wrote:

> Building djvulibre-3.5.21 with gcc4, while linking libdjvulibre:
> .libs/atomic.o:atomic.cpp:(.text+0x3b): undefined reference to
> `___sync_bool_compare_and_swap_4'
> .libs/atomic.o:atomic.cpp:(.text+0x65): undefined reference to
> `___sync_add_and_fetch_4'
> Some googling shows that the culprit *may be* gcc4:
> Any ideas?

  Well, I guess the question is, what's the minimum level of CPU we want to
support, and I can configure the next version --with-arch that level, and as
long as it's >=486 we'll be ok.  I think the question is mainly "686, or is
there any reason to have 586 as the minimum supported CPU"?

  (Not that < [56]86 users couldn't add the -march= flag to their builds, but
this will determine what minimum level of cpu all the default code is
generated for, and as most packages will be built with the default, we run the
risk of having things in the distro that they can't install and run
successfully from binaries.)


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]