Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(622)

Issue 7576004: Force libjpeg_turbo to use MMX (Closed)

Created:
9 years, 4 months ago by Timur Iskhodzhanov
Modified:
9 years, 4 months ago
Reviewers:
Derek Bruening
CC:
chromium-reviews, Alexander Potapenko, pam+watch_chromium.org, stuartmorgan+watch_chromium.org
Visibility:
Public.

Description

Force libjpeg_turbo to use MMX TBR=bruening Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=95419

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -0 lines) Patch
M tools/valgrind/valgrind_test.py View 1 chunk +1 line, -0 lines 1 comment Download

Messages

Total messages: 3 (0 generated)
Timur Iskhodzhanov
TBR
9 years, 4 months ago (2011-08-04 14:52:35 UTC) #1
Derek Bruening
http://codereview.chromium.org/7576004/diff/1/tools/valgrind/valgrind_test.py File tools/valgrind/valgrind_test.py (right): http://codereview.chromium.org/7576004/diff/1/tools/valgrind/valgrind_test.py#newcode736 tools/valgrind/valgrind_test.py:736: "JSIMD_FORCEMMX" : "0", # http://code.google.com/p/drmemory/issues/detail?id=540 shouldn't this be set ...
9 years, 4 months ago (2011-08-04 14:54:27 UTC) #2
Timur Iskhodzhanov
9 years, 4 months ago (2011-08-04 15:58:54 UTC) #3
D'oh!
This's what happens when you commit in the last 5 minutes before running to
something else :(

Powered by Google App Engine
This is Rietveld 408576698