Closed
Bug 143461
Opened 24 years ago
Closed 24 years ago
nsWebBrowserPersist.cpp creates internal compiler error in xlC 3.6.4
Categories
(Core :: Networking: File, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: david, Assigned: jdunn)
Details
(Keywords: qawanted)
Attachments
(1 file)
|
830 bytes,
patch
|
Brade
:
review+
alecf
:
superreview+
|
Details | Diff | Splinter Review |
The line:
msgId = aIsReadError ? NS_LITERAL_STRING("readError") :
NS_LITERAL_STRING("writeError");
creates an internal compiler error. I have tried several ways to rewrite
this line and am unsure if I am doing it correctly. Let me know how you
would rewrite this line.
Thanks.
if (aIsReadError) {
msgId = NS_LITERAL_STRING("readError");
} else {
msgId = NS_LITERAL_STRING("writeError");
}
What is xlC?
The if/else should do the trick, but it sounds like the compiler has a problem
(with Unichar strings?) if it can't compile something like this.
xlC is the c++ compiler on AIX.
Yes xlC has a problem but it is based on how
msgId = aIsReadError ? NS_LITERAL_STRING("readError") :
NS_LITERAL_STRING("writeError");
and how temporary variables/registers are used and then
assigned.
The fact that msgID = NS_LITERAL_STRING("readError")
works but the above doesn't indicates that it is not so much
an issue with Unichar strings but more on the code syntax
and how NS_LITERAL_STRING is defined.
Comment 5•24 years ago
|
||
does the if() version work? if so, we should just go with that. what type is msgId?
Comment 8•24 years ago
|
||
Comment on attachment 84311 [details] [diff] [review]
This patch works for me on xlC 3.6.4
r=brade
Attachment #84311 -
Flags: review+
Comment 9•24 years ago
|
||
Comment on attachment 84311 [details] [diff] [review]
This patch works for me on xlC 3.6.4
sr=alecf
Attachment #84311 -
Flags: superreview+
| Assignee | ||
Comment 10•24 years ago
|
||
fix checked into trunk
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 12•23 years ago
|
||
I am no longer compiling mozilla, so am unable to verify the fix.
You need to log in
before you can comment on or make changes to this bug.
Description
•