Subscribe: Comments on: Cargo Cult Programming
http://www.airs.com/blog/archives/294/feed
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
comment  gcc interprets  gcc  ian lance  ian  interprets volatile  lance taylor  lance  suggest volatile  taylor  volatile gcc  volatile   
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Comments on: Cargo Cult Programming

Comments for Airs – Ian Lance Taylor



Ian Lance Taylor



Last Build Date: Tue, 19 Dec 2017 15:49:28 +0000

 



Comment on const by Why would you use the keyword const if you already know variable should be constant? - ExceptionsHub

Tue, 19 Dec 2017 15:49:28 +0000

[…] is a good explanation from Ian Lance Taylor (who worked on gcc and gold […]



Comment on Linkers part 1 by A journey into Radare 2 – Part 2: Exploitation – Megabeets

Sun, 03 Sep 2017 16:32:14 +0000

[…] the function address from the GOT. To read more about the linking process, I highly recommend this series of articles about linkers by Ian Lance […]



Comment on Go experience report: the append function by Are We There Yet: The Go Generics Debate – Brave New Geek

Tue, 25 Jul 2017 14:06:38 +0000

[…] Lance Taylor’s recent post shows there is a divide within the Go team regarding generics. He tells the story of how the copy() […]



Comment on volatile by Does a memory barrier tame Microsoft’s optimizer? | Solutions for enthusiast and professional programmers

Sun, 02 Aug 2015 17:21:56 +0000

[…] And for those who suggest volatile, we can’t use it under GCC because GCC interprets the volatile keyword differently than Microsoft. See the same thread for a discussion; or see Ian Lance Taylor’s blog on Volatile. […]



Comment on volatile by Does a memory barrier tame Microsoft's optimizer? | C++

Sun, 02 Aug 2015 00:46:58 +0000

[…] And for those who suggest volatile, we can’t use it under GCC because GCC interprets the volatile keyword differently than Microsoft. See the same thread for a discussion; or see Ian Lance Taylor’s blog on Volatile. […]