Linux sandbox: add space for 8 parameters to the Syscall() class

sandbox/linux/seccomp-bpf/syscall.cc

Index: sandbox/linux/seccomp-bpf/syscall.cc
diff --git a/sandbox/linux/seccomp-bpf/syscall.cc b/sandbox/linux/seccomp-bpf/syscall.cc
index 64c0b8eb9b41b708482571febc4d417b3e1110c4..b7fce95ea4c38fa7b16abff03551df7777cb4a16 100644
--- a/sandbox/linux/seccomp-bpf/syscall.cc
+++ b/sandbox/linux/seccomp-bpf/syscall.cc
@@ -181,7 +181,9 @@ intptr_t Syscall::Call(int nr,
                        intptr_t p2,
                        intptr_t p3,
                        intptr_t p4,
-                       intptr_t p5) {
+                       intptr_t p5,
+                       intptr_t p6,
+                       intptr_t p7) {
   // We rely on "intptr_t" to be the exact size as a "void *". This is
   // typically true, but just in case, we add a check. The language
   // specification allows platforms some leeway in cases, where
@@ -192,6 +194,8 @@ intptr_t Syscall::Call(int nr,
   COMPILE_ASSERT(sizeof(void*) == sizeof(intptr_t),
                  pointer_types_and_intptr_must_be_exactly_the_same_size);
 
+  // TODO(nedeljko): Enable use of more than six parameters on architectures

[mdempsky, 2014/07/01 21:53:17]

Would it make sense to add DCHECK()s to make sure p6 == 0 and p7 == 0 until
support is added?

[nedeljko, 2014/07/02 10:46:19]

Done.

+  //                 where that makes sense.
   const intptr_t args[6] = {p0, p1, p2, p3, p4, p5};
 
 // Invoke our file-scope assembly code. The constraints have been picked