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

Issue 22903028: Make x87 stack tracking more robust and avoid spilling (Closed)

Created:
7 years, 4 months ago by oliv
Modified:
7 years, 3 months ago
Reviewers:
titzer, Toon Verwaest
CC:
v8-dev
Visibility:
Public.

Description

Make x87 stack tracking more robust and avoid spilling BUG=

Patch Set 1 : #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+202 lines, -66 lines) Patch
M src/flag-definitions.h View 1 chunk +1 line, -0 lines 0 comments Download
M src/ia32/assembler-ia32.h View 1 chunk +1 line, -1 line 0 comments Download
M src/ia32/lithium-codegen-ia32.h View 5 chunks +21 lines, -15 lines 0 comments Download
M src/ia32/lithium-codegen-ia32.cc View 14 chunks +164 lines, -38 lines 1 comment Download
M src/ia32/lithium-gap-resolver-ia32.cc View 1 chunk +8 lines, -3 lines 0 comments Download
M src/ia32/lithium-ia32.h View 2 chunks +5 lines, -7 lines 0 comments Download
M src/ia32/lithium-ia32.cc View 2 chunks +2 lines, -2 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
oliv
7 years, 4 months ago (2013-08-22 12:40:06 UTC) #1
Toon Verwaest
This approach seems pretty complex. As discussed, I'm not sure it's the right way to ...
7 years, 4 months ago (2013-08-22 13:33:40 UTC) #2
oliv
7 years, 3 months ago (2013-08-23 09:27:16 UTC) #3
On 2013/08/22 13:33:40, Toon Verwaest wrote:
> This approach seems pretty complex. As discussed, I'm not sure it's the right
> way to go.
> 
>
https://codereview.chromium.org/22903028/diff/5001/src/ia32/lithium-codegen-i...
> File src/ia32/lithium-codegen-ia32.cc (right):
> 
>
https://codereview.chromium.org/22903028/diff/5001/src/ia32/lithium-codegen-i...
> src/ia32/lithium-codegen-ia32.cc:744: continue;
> As discussed, this seems broken. If we swap input variables downwards, we'll
> visit them again and they'll seem like input variables again; and we won't pop
> non-input-variables we just swapped. Additionally, in larger stacks, we'll
never
> manage to get input variables that are being swapped upwards in the right
> position.
> 
> I also don't like this kind of code at all; it's very hard to understand.

ok, lets put this on hold as it doesn't really pay off. i'll just try to fix the
immediate problems then...

Powered by Google App Engine
This is Rietveld 408576698