Revert of 32-bit linux: Force 16-byte stack alignment.

Revert of 32-bit linux: Force 16-byte stack alignment. (patchset #1 id:1 of https://codereview.chromium.org/1899783002/ )

Reason for revert:
Broke InterpreterCreateArguments test on Linux nosnap debug:

https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%20debug/builds/6404

Original issue's description:
> 32-bit linux: Force 16-byte stack alignment.
>
> clang assumes 16-byte stack alignment, but incoming stack alignment isn't
> always guaranteed to be that way.  It looks like v8 was lucky to not hit
> this so far.
>
> See https://crbug.com/418554 -- this makes v8's standalone config match
> Chromium.  See also https://llvm.org/bugs/show_bug.cgi?id=21414
>
> Maybe it's possible to change the caller of OnEntryHook() to guarantee
> the right alignment, but matching Chromium's build flags here seems like
> a good idea in general.
>
> BUG=v8:4928
> LOG=n
>
> Committed: https://crrev.com/3afb3324941625559635380ef98a2ee73e370a0a
> Cr-Commit-Position: refs/heads/master@{#35597}

TBR=machenbach@chromium.org,rnk@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:4928
Committed: https://crrev.com/8292435baa2c66fc7146f06ab0c088cc9b58d835
Cr-Commit-Position: refs/heads/master@{#35599}

[adamk, 2016-04-18 22:00:01]

Created Revert of 32-bit linux: Force 16-byte stack alignment.

[commit-bot: I haz the power, 2016-04-18 22:00:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1895783004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1895783004/1

[commit-bot: I haz the power, 2016-04-18 22:00:27]

Description was changed from

==========
Revert of 32-bit linux: Force 16-byte stack alignment. (patchset #1 id:1 of
https://codereview.chromium.org/1899783002/ )

Reason for revert:
Broke InterpreterCreateArguments test on Linux nosnap debug:

https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%2...

Original issue's description:
> 32-bit linux: Force 16-byte stack alignment.
> 
> clang assumes 16-byte stack alignment, but incoming stack alignment isn't
> always guaranteed to be that way.  It looks like v8 was lucky to not hit
> this so far.
> 
> See https://crbug.com/418554 -- this makes v8's standalone config match
> Chromium.  See also https://llvm.org/bugs/show_bug.cgi?id=21414
> 
> Maybe it's possible to change the caller of OnEntryHook() to guarantee
> the right alignment, but matching Chromium's build flags here seems like
> a good idea in general.
> 
> BUG=v8:4928
> LOG=n
> 
> Committed: https://crrev.com/3afb3324941625559635380ef98a2ee73e370a0a
> Cr-Commit-Position: refs/heads/master@{#35597}

TBR=machenbach@chromium.org,rnk@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:4928
==========

to

==========
Revert of 32-bit linux: Force 16-byte stack alignment. (patchset #1 id:1 of
https://codereview.chromium.org/1899783002/ )

Reason for revert:
Broke InterpreterCreateArguments test on Linux nosnap debug:

https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%2...

Original issue's description:
> 32-bit linux: Force 16-byte stack alignment.
> 
> clang assumes 16-byte stack alignment, but incoming stack alignment isn't
> always guaranteed to be that way.  It looks like v8 was lucky to not hit
> this so far.
> 
> See https://crbug.com/418554 -- this makes v8's standalone config match
> Chromium.  See also https://llvm.org/bugs/show_bug.cgi?id=21414
> 
> Maybe it's possible to change the caller of OnEntryHook() to guarantee
> the right alignment, but matching Chromium's build flags here seems like
> a good idea in general.
> 
> BUG=v8:4928
> LOG=n
> 
> Committed: https://crrev.com/3afb3324941625559635380ef98a2ee73e370a0a
> Cr-Commit-Position: refs/heads/master@{#35597}

TBR=machenbach@chromium.org,rnk@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:4928
==========

[commit-bot: I haz the power, 2016-04-18 22:00:29]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-18 22:01:55]

Description was changed from

==========
Revert of 32-bit linux: Force 16-byte stack alignment. (patchset #1 id:1 of
https://codereview.chromium.org/1899783002/ )

Reason for revert:
Broke InterpreterCreateArguments test on Linux nosnap debug:

https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%2...

Original issue's description:
> 32-bit linux: Force 16-byte stack alignment.
> 
> clang assumes 16-byte stack alignment, but incoming stack alignment isn't
> always guaranteed to be that way.  It looks like v8 was lucky to not hit
> this so far.
> 
> See https://crbug.com/418554 -- this makes v8's standalone config match
> Chromium.  See also https://llvm.org/bugs/show_bug.cgi?id=21414
> 
> Maybe it's possible to change the caller of OnEntryHook() to guarantee
> the right alignment, but matching Chromium's build flags here seems like
> a good idea in general.
> 
> BUG=v8:4928
> LOG=n
> 
> Committed: https://crrev.com/3afb3324941625559635380ef98a2ee73e370a0a
> Cr-Commit-Position: refs/heads/master@{#35597}

TBR=machenbach@chromium.org,rnk@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:4928
==========

to

==========
Revert of 32-bit linux: Force 16-byte stack alignment. (patchset #1 id:1 of
https://codereview.chromium.org/1899783002/ )

Reason for revert:
Broke InterpreterCreateArguments test on Linux nosnap debug:

https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap%20-%2...

Original issue's description:
> 32-bit linux: Force 16-byte stack alignment.
>
> clang assumes 16-byte stack alignment, but incoming stack alignment isn't
> always guaranteed to be that way.  It looks like v8 was lucky to not hit
> this so far.
>
> See https://crbug.com/418554 -- this makes v8's standalone config match
> Chromium.  See also https://llvm.org/bugs/show_bug.cgi?id=21414
>
> Maybe it's possible to change the caller of OnEntryHook() to guarantee
> the right alignment, but matching Chromium's build flags here seems like
> a good idea in general.
>
> BUG=v8:4928
> LOG=n
>
> Committed: https://crrev.com/3afb3324941625559635380ef98a2ee73e370a0a
> Cr-Commit-Position: refs/heads/master@{#35597}

TBR=machenbach@chromium.org,rnk@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:4928

Committed: https://crrev.com/8292435baa2c66fc7146f06ab0c088cc9b58d835
Cr-Commit-Position: refs/heads/master@{#35599}
==========

[commit-bot: I haz the power, 2016-04-18 22:01:55]

Patchset 1 (id:??) landed as
https://crrev.com/8292435baa2c66fc7146f06ab0c088cc9b58d835
Cr-Commit-Position: refs/heads/master@{#35599}