This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/53292] multi-threaded (OpenMP) is slower than single-threaded
- From: "fh_p at hotmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 09 May 2012 12:53:46 +0000
- Subject: [Bug c++/53292] multi-threaded (OpenMP) is slower than single-threaded
- Auto-submitted: auto-generated
- References: <bug-53292-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53292
--- Comment #4 from FH <fh_p at hotmail dot com> 2012-05-09 12:53:46 UTC ---
I don't understand your answer.
Timing just times the for loop. Checking array content is single threaded :
this is added to make sure the for loop has done the job correctly and this
check is not timed. The array to initialize is shared by threads (shared by
default) ans not private to each thread.
To me, the test seems relevant. If it's not, why ? And how to modify it ?