Issue 9117014: Use memcpy() instead of violating strict-aliasing rules.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 9117014: Use memcpy() instead of violating strict-aliasing rules. (Closed)

Created:
8 years, 11 months ago by Evan Martin

Modified:
8 years, 11 months ago

Reviewers:
Yusuke Sato

CC:
chromium-reviews

Base URL:
http://ots.googlecode.com/svn/trunk/

Visibility:
Public.

Use memcpy() instead of violating strict-aliasing rules. (This is the approach suggested by the standard. Modern compilers inline memcpy anyway.)

Created: 8 years, 11 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+3 lines, -2 lines)			Patch
	M	include/opentype-sanitiser.h	View		1 chunk	+3 lines, -2 lines	0 comments	Download

Total messages: 3 (0 generated)

Yusuke Sato

8 years, 11 months ago (2012-01-24 09:45:57 UTC) #3

submitted to the OTS repository in r80 and rolled Chrome DEPS.