byte order dependency in XDR'd strings

VERIFIED INVALID

Status

()

Core
JavaScript Engine
P2
normal
VERIFIED INVALID
20 years ago
16 years ago

People

(Reporter: shaver, Assigned: brendan)

Tracking

Trunk
All
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(This bug imported from BugSplat, Netscape's internal bugsystem.  It
was known there as bug #299794
http://scopus.netscape.com/bugsplat/show_bug.cgi?id=299794
Imported into Bugzilla on 01/27/99 15:35)

Strings produced by Script.prototype.freeze have a byte-order dependency.

From Bernhard Marschall (bmarsch@hyperwave.com):
> After taking a closer look, I got the impression the byte-swapping is done
> twice: once by the JS_XDRxxx calls and once in the #ifdef IS_BIG_ENDIAN
> section in script_freeze.

Comment 1

20 years ago
Marked TFV 1.4 indicating we want this bug fixed for 1.4.

Comment 2

20 years ago
Marking TFV blank; not required for 1.4.

Comment 3

19 years ago
this bug belongs with Norris now.

bjorn
(Assignee)

Updated

19 years ago
Assignee: norris → brendan
Hardware: All
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID

Comment 4

19 years ago
The byte-swapping is necessary to make strings (unicode vectors) platform
independent.  Viewed as byte-vectors, they'll have different contents depending
on endian-ness -- but the byte-vector in one machine is never visible to another
(only strings may be passed among machines).

/be

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 5

19 years ago
Changing component to "Javascript Engine".  "Javascript" component is being
retired.

Comment 6

19 years ago
Changing component to "Javascript Engine".  "Javascript" component is being

retired.
You need to log in before you can comment on or make changes to this bug.