[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: relocation R_X86_64_PC32



On Thu, 2006-07-20 at 07:06 -0500, Rex Dieter wrote:
> Caolan McNamara wrote:
> 
> > On Wed, 2006-07-19 at 11:18 -0500, Rex Dieter wrote:
> >> Rex Dieter wrote:
> >> 
> >
> > Try disabling visibility support, it doesn't currently work in the devel
> > gcc the way qt probably expects it to, i.e. add
> >  "-no-reduce-exports" 
> > to your qt4.spec's configure line
> 
> Thanks.   Is there a bugzilla on this and/or when can we expect -fvisibility
> to be fixed?

There's a big chat about it at
http://gcc.gnu.org/ml/gcc/2006-07/threads.html#00204
I don't know if visibility should actually be called "broken" so as to
be fixed, but it has changed sufficiently that existing markup doesn't
really cut it anymore :-(

> 
> > p.s. I suggest adding -fno-strict-aliasing to your compile flags, there
> > are a lot of warnings about aliasing issues in that build which are
> > likely to be real problems.
> 
> In "that build" you mean that build of gcc?  So this only affects the
> fc6/devel branch (for now)?

No, I just meant that from that build.log I can see plenty of warnings
about "dereferencing type-punned pointer will break strict-aliasing
rules"
http://buildsys.fedoraproject.org/logs/fedora-development-extras/12668-qt4-4.1.4-6.fc6/x86_64/build.log
That's not a new thing, nor is it a problem of gcc, but generally is a
real warning that the code is somewhat busted, but -fno-strict-aliasing
will avoid the problems that this optimization would otherwise trigger
in the dodgy code.

C.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]