diff options
author | markus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-07-15 18:50:46 +0000 |
---|---|---|
committer | markus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-07-15 18:50:46 +0000 |
commit | ff64b0c5a1f35cce56bdab3ae22d420066bd8bb4 (patch) | |
tree | 64d6cc340989a1cb05afa7b77837836da8b2a8d5 /DEPS | |
parent | d4e3221a0a91af1dd96a978c100b9d2c96084ea2 (diff) | |
download | chromium_src-ff64b0c5a1f35cce56bdab3ae22d420066bd8bb4.zip chromium_src-ff64b0c5a1f35cce56bdab3ae22d420066bd8bb4.tar.gz chromium_src-ff64b0c5a1f35cce56bdab3ae22d420066bd8bb4.tar.bz2 |
- Unconditionally allow p{read,write}{,v}().
- clang complains about unused values computed by C expressions
- clang makes extensive use of SSE registers. This requires us to
explicitly align the stack pointer in x86-32. It seems as if x86-64
already works correctly, but we might need to revisit this assessment
if we encounter problems.
- clang doesn't implicitly do a const_cast() when it does a
reinterpret_cast(). We now do a C-style cast instead, as that ends
up being more readable.
- the code should now compile with clang, but it still doesn't behave
quite correctly. Do not use seccomp&clang in production until I commit
the next set of changes.
Review URL: http://codereview.chromium.org/7394001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92722 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
-rw-r--r-- | DEPS | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -32,7 +32,7 @@ deps = { (Var("googlecode_url") % "google-url") + "/trunk@159", "src/seccompsandbox": - (Var("googlecode_url") % "seccompsandbox") + "/trunk@155", + (Var("googlecode_url") % "seccompsandbox") + "/trunk@158", "src/sdch/open-vcdiff": (Var("googlecode_url") % "open-vcdiff") + "/trunk@28", |