[Bug middle-end/21628] GCC much slower than ICL. Lack of inlining?

2008-09-28 Thread laurent at ient dot rwth-aachen dot de
--- Comment #9 from laurent at ient dot rwth-aachen dot de 2008-09-28 07:59 --- (In reply to comment #8) Try #define inline inline __attribute__((always_inline)) instead. The inline keyword changes linkage, so you have to keep it. If you keep having problems open a new bugreport

[Bug middle-end/21628] GCC much slower than ICL. Lack of inlining?

2008-09-27 Thread laurent at ient dot rwth-aachen dot de
--- Comment #7 from laurent at ient dot rwth-aachen dot de 2008-09-27 11:40 --- Hello I reopen the discussion because I noticed a problem in relation with __attribute__((__always_inline__)) when I tried to compile my library as a DLL. GCC now forces inlines well, and is now as quick

[Bug middle-end/21628] GCC much slower than ICL. Lack of inlining?

2007-11-16 Thread laurent at ient dot rwth-aachen dot de
--- Comment #2 from laurent at ient dot rwth-aachen dot de 2007-11-16 17:46 --- (In reply to comment #1) What does -Winline say? Have you tried with always_inline? Example: /* Prototype. */ inline void foo (const char) __attribute__((always_inline)); Whaow, I have

[Bug middle-end/21628] GCC much slower than ICL. Lack of inlining?

2007-11-16 Thread laurent at ient dot rwth-aachen dot de
--- Comment #6 from laurent at ient dot rwth-aachen dot de 2007-11-16 20:42 --- Note that for completely inlining kernels you can use the __attribute__((flatten)) on the *calling* function. Usually with expression templates that is the function containing the loops, like void

[Bug c++/21628] New: GCC much slower than ICL. Lack of inlining?

2005-05-17 Thread laurent at ient dot rwth-aachen dot de
Version: 3.4.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: laurent at ient dot rwth-aachen dot de CC: gcc-bugs at gcc dot gnu dot org http