lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150618131022.3f502e60@gandalf.local.home>
Date:	Thu, 18 Jun 2015 13:10:22 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>, umgwanakikbuti@...il.com,
	mingo@...e.hu, ktkhai@...allels.com, tglx@...utronix.de,
	juri.lelli@...il.com, pang.xunlei@...aro.org, oleg@...hat.com,
	wanpeng.li@...ux.intel.com, linux-kernel@...r.kernel.org,
	Al Viro <viro@...IV.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 11/18] seqcount: Introduce raw_write_seqcount_barrier()

On Thu, 18 Jun 2015 09:54:07 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:

> Yep, I have to frequently remind them that most projects need to support
> old compilers.  And I did point out that the commentary at the end
> of that document would not encourage adoption of C11.  They of course
> felt this was unfair of me, so I have to thank you both for proving the
> correctness of my reply to them.  Although you guys didn't use quite as
> many swear words as I would have expected.  ;-)

I could add a few more if you would like ;-)


What's their issue? Is there some kind of benchmark war going on
between different compilers? Where they want want to prove they can
produce the absolute fastest code possible, but only use single
threaded apps and screw those that must support multi-threaded
applications.

My phone and my camera have multicore systems. Single threaded is not
the way of the future. Which ever compiler makes it easier to write
multi-threaded applications is going to win, regardless of how well a
compiler can claim they optimize code the best for a single threaded
app.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ