Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-20 Thread Thiago Macieira
On terça-feira, 20 de agosto de 2013 07:23:28, Knoll Lars wrote: > Here's another idea (no idea if we could make it work though): If the > methods don't expose any of the Qt types as API, we could try putting all > the #include's that we use in the implementation into an anonymous > namespace. Tha

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-20 Thread Knoll Lars
On 20.08.13 09:15, "Thiago Macieira" wrote: >On terça-feira, 20 de agosto de 2013 06:24:01, Knoll Lars wrote: >> A slightly hacky solution might be to force inlining of inline methods >>in >> these files. With gcc, we could achieve that by defining inline to >> __attribute__((always_inline)) on

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-20 Thread Thiago Macieira
On terça-feira, 20 de agosto de 2013 06:24:01, Knoll Lars wrote: > A slightly hacky solution might be to force inlining of inline methods in > these files. With gcc, we could achieve that by defining inline to > __attribute__((always_inline)) on the top of the file that's being > compiled. That do

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-19 Thread Knoll Lars
On 20.08.13 03:54, "Thiago Macieira" wrote: >On quinta-feira, 15 de agosto de 2013 08:06:19, Thiago Macieira wrote: >> > I'd agree that option (4) is the cleanest solution. Have you checked >>how >> > much we'd need to change to implement it? >> >> No, not yet. >> >> I don't think it will be

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-19 Thread Thiago Macieira
On quinta-feira, 15 de agosto de 2013 08:06:19, Thiago Macieira wrote: > > I'd agree that option (4) is the cleanest solution. Have you checked how > > much we'd need to change to implement it? > > No, not yet. > > I don't think it will be too hard because those routines are still fairly > limit

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-19 Thread Thiago Macieira
On segunda-feira, 19 de agosto de 2013 07:56:43, Koehne Kai wrote: > > We recommend people set the environment if they want different flags, > > besides the stock from their compilers. > > Where do we recommend this? E.g. > > http://qt-project.org/doc/qt-5.0/qtdoc/install-x11.html > > just says

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-19 Thread Karl Ruetz
eira Sent: Monday, August 19, 2013 9:42 AM To: development@qt-project.orgSubject: Re: [Development] QTBUG-30440: restricting the SIMD files On segunda-feira, 19 de agosto de 2013 07:37:58, Koehne Kai wrote: >>> >>>> I don't know how big the performance gains really are, but

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-19 Thread Thiago Macieira
On segunda-feira, 19 de agosto de 2013 07:37:58, Koehne Kai wrote: > I don't know how big the performance gains really are, but if it's > noticeable, why not switch the default for everyone using the default > mkspec? Switching the default means making it difficult to unset for those who want it

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-16 Thread Thiago Macieira
On quinta-feira, 15 de agosto de 2013 12:04:36, Thiago Macieira wrote: > For MSVC, set CFLAGS on x86 to -arch:SSE2. Actually, this is now the default on MSVC 2012. So I suggest we use that version to compile Creator for the SDK, and leave the Qt build to the native flags of the compiler in quest

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-16 Thread Thiago Macieira
On sexta-feira, 16 de agosto de 2013 11:53:45, Koehne Kai wrote: > > I recommend: > > CFLAGS (x86) = -march=i686 -mtune=core2 -msse2 -mfpmath=sse > > CFLAGS (x86-64) = -mtune=core2 > > LFLAGS = -Wl,-O1 -Wl,--as-needed -Wl,-z,relro > > > > > > > > For MSVC, set CFLAGS on x86 to -a

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-15 Thread Thiago Macieira
On quinta-feira, 15 de agosto de 2013 17:01:49, Knoll Lars wrote: > On 8/15/13 5:07 PM, "Sune Vuorela" wrote: > >On 2013-08-15, Thiago Macieira wrote: > >> Uh... no, I don't think we can assume that. I'm afraid of Sune and > >> > >>other > >> > >> distro packagers! :-) > > > >*whistles innocently

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-15 Thread Thiago Macieira
On quinta-feira, 15 de agosto de 2013 20:20:04, Oswald Buddenhagen wrote: > On Thu, Aug 15, 2013 at 05:01:49PM +, Knoll Lars wrote: > > On 8/15/13 5:07 PM, "Sune Vuorela" wrote: > > >On 2013-08-15, Thiago Macieira wrote: > > >> Uh... no, I don't think we can assume that. I'm afraid of Sune an

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-15 Thread Thiago Macieira
On quinta-feira, 15 de agosto de 2013 12:57:04, Knoll Lars wrote: > >What's more, on x86, the default 32-bit build is just nonsense today. > >CPUs > >from the past 10 years from both Intel and AMD have had support for SSE2. > > THat's a somewhat separate problem, but I agree that it's time to fix

Re: [Development] QTBUG-30440: restricting the SIMD files

2013-08-14 Thread Thiago Macieira
On quinta-feira, 15 de agosto de 2013 14:20:31, Christian Gagneraud wrote: > > 1) Drop simd.prf and the runtime checking > > > > This means dropping the special builds. We'd #include the special files if > > the user is building Qt for a special target. > > Can't you get rid of these special file

[Development] QTBUG-30440: restricting the SIMD files

2013-08-14 Thread Thiago Macieira
Hello all I've been running through this problem for a while. I might have finally a solution, but I'd like to see if there are other options and which of the solutions we should go for. == Quick medium-sized summary of the problem: https://bugreports.qt-project.org/browse/QTBUG-30440