Closed
Bug 596545
Opened 15 years ago
Closed 15 years ago
nanojit: Add more calling-convention tests.
Categories
(Core Graveyard :: Nanojit, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jbramley, Assigned: jbramley)
Details
(Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey[suspect-regress-ts_cold_generated_med][suspect-regress-dromaeo_css][suspect-regress-dromaeo_jslib])
Attachments
(1 file)
|
3.08 KB,
patch
|
n.nethercote
:
review+
|
Details | Diff | Splinter Review |
No description provided.
| Assignee | ||
Comment 1•15 years ago
|
||
These tests exercise the ARM calling convention(s). They are valid for other architectures, but it might be worth adding more tests that exercise similar paths in other back-ends.
Attachment #475468 -
Flags: review?
| Assignee | ||
Comment 2•15 years ago
|
||
Comment on attachment 475468 [details] [diff] [review]
Add calling tests with mixed argument types.
Oops. I forgot to tag a reviewer.
Attachment #475468 -
Flags: review? → review?(nnethercote)
Comment 3•15 years ago
|
||
Comment on attachment 475468 [details] [diff] [review]
Add calling tests with mixed argument types.
> double calld1(double x, double i, double y, double l, double x1, double i1, double y1, double l1) {
> return x + i * y - l + x1 / i1 - y1 * l1;
> }
>
>+// The calling tests with mixed argument types are sensible for all platforms, but they highlight
>+// the differences between the supported ABIs on ARM.
>+
>+double calld2(int i, double x, double y, int j, int k, double z) {
>+ return (x + y + z) / (double)(i + j + k);
>+}
>+
>+double calld3(int i, int j, int k, double x) {
>+ return x / (double)(i + j + k);
>+}
>+
>+double calld4(int i, int j, double x, int k, double y, double z) {
>+ return (x + y + z) / (double)(i + j + k);
>+}
The names calld[234] don't make much sense since there are a mix of int and double args. Maybe callid[123]? Otherwise it looks good.
Attachment #475468 -
Flags: review?(nnethercote) → review+
| Assignee | ||
Comment 4•15 years ago
|
||
Whiteboard: fixed-in-nanojit
Comment 5•15 years ago
|
||
Whiteboard: fixed-in-nanojit → fixed-in-nanojit, fixed-in-tracemonkey
Comment 6•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey → fixed-in-nanojit, fixed-in-tracemonkey[suspect-regress-ts_cold_generated_med]
Comment 7•15 years ago
|
||
A changeset from this bug was associated with a XP Ts, Cold MED Dirty Profile regression on Firefox. boo-urns :(
Previous: avg 420.356 stddev 3.679 of 30 runs up to a9d1ad0bc386
New : avg 430.832 stddev 1.905 of 5 runs since a60414d076b5
Change : +10.475 (2.49% / z=2.847)
Graph : http://mzl.la/bZFaB3
The regression occurred from changesets in the following range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a9d1ad0bc386&tochange=a60414d076b5
The tag [suspect-regress-ts_cold_generated_med] has been added to the status whiteboard;
please remove it only once you have confirmed this bug is not the cause
of the regression.
Updated•15 years ago
|
Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey[suspect-regress-ts_cold_generated_med] → fixed-in-nanojit, fixed-in-tracemonkey[suspect-regress-ts_cold_generated_med][suspect-regress-dromaeo_css]
Comment 8•15 years ago
|
||
A changeset from this bug was associated with a Win7 Dromaeo (CSS) regression on Firefox. boo-urns :(
Previous: avg 2014.419 stddev 40.480 of 30 runs up to a9d1ad0bc386
New : avg 1901.610 stddev 12.432 of 5 runs since a60414d076b5
Change : -112.809 (-5.6% / z=2.787)
Graph : http://mzl.la/9gFu4n
The regression occurred from changesets in the following range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a9d1ad0bc386&tochange=a60414d076b5
The tag [suspect-regress-dromaeo_css] has been added to the status whiteboard;
please remove it only once you have confirmed this bug is not the cause
of the regression.
Updated•15 years ago
|
Whiteboard: fixed-in-nanojit, fixed-in-tracemonkey[suspect-regress-ts_cold_generated_med][suspect-regress-dromaeo_css] → fixed-in-nanojit, fixed-in-tracemonkey[suspect-regress-ts_cold_generated_med][suspect-regress-dromaeo_css][suspect-regress-dromaeo_jslib]
Comment 9•15 years ago
|
||
A changeset from this bug was associated with a Win7 Dromaeo (jslib) regression on Firefox. boo-urns :(
Previous: avg 127.610 stddev 4.222 of 30 runs up to a9d1ad0bc386
New : avg 116.384 stddev 0.751 of 5 runs since a60414d076b5
Change : -11.226 (-8.8% / z=2.659)
Graph : http://mzl.la/bZu5UP
The regression occurred from changesets in the following range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a9d1ad0bc386&tochange=a60414d076b5
The tag [suspect-regress-dromaeo_jslib] has been added to the status whiteboard;
please remove it only once you have confirmed this bug is not the cause
of the regression.
Comment 10•15 years ago
|
||
A changeset from this bug was associated with a XP Dromaeo (CSS) regression on Firefox. boo-urns :(
Previous: avg 2045.275 stddev 49.676 of 30 runs up to a9d1ad0bc386
New : avg 1936.120 stddev 13.937 of 5 runs since a60414d076b5
Change : -109.155 (-5.34% / z=2.197)
Graph : http://mzl.la/b0dlou
The regression occurred from changesets in the following range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a9d1ad0bc386&tochange=a60414d076b5
The tag [suspect-regress-dromaeo_css] has been added to the status whiteboard;
please remove it only once you have confirmed this bug is not the cause
of the regression.
Comment 11•15 years ago
|
||
A changeset from this bug was associated with a XP Dromaeo (jslib) regression on Firefox. boo-urns :(
Previous: avg 129.703 stddev 4.099 of 30 runs up to a9d1ad0bc386
New : avg 117.954 stddev 0.660 of 5 runs since a60414d076b5
Change : -11.749 (-9.06% / z=2.866)
Graph : http://mzl.la/avZij4
The regression occurred from changesets in the following range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a9d1ad0bc386&tochange=a60414d076b5
The tag [suspect-regress-dromaeo_jslib] has been added to the status whiteboard;
please remove it only once you have confirmed this bug is not the cause
of the regression.
Updated•12 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•