Closed
Bug 1200097
Opened 11 years ago
Closed 11 years ago
Fix warnings in logalloc
Categories
(Core :: Memory Allocator, defect)
Core
Memory Allocator
Tracking
()
RESOLVED
FIXED
mozilla43
| Tracking | Status | |
|---|---|---|
| firefox43 | --- | fixed |
People
(Reporter: n.nethercote, Assigned: n.nethercote)
References
Details
Attachments
(1 file)
|
2.01 KB,
patch
|
glandium
:
review+
|
Details | Diff | Splinter Review |
FdPrintf.c has one warning that shows up in two different directories.
| Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8654701 -
Flags: review?(mh+mozilla)
Comment 2•11 years ago
|
||
Comment on attachment 8654701 [details] [diff] [review]
Fix warnings in logalloc
Review of attachment 8654701 [details] [diff] [review]:
-----------------------------------------------------------------
::: memory/replace/logalloc/FdPrintf.cpp
@@ +125,5 @@
> // See comment in FdPrintf.h as to why WriteFile is used.
> DWORD written;
> WriteFile(reinterpret_cast<HANDLE>(aFd), buf, b - buf, &written, nullptr);
> #else
> + mozilla::unused << write(aFd, buf, b - buf);
Ideally, this should just actually care about the result (especially if it's -1 and errno is EINTR). But meh.
Attachment #8654701 -
Flags: review?(mh+mozilla) → review+
Comment 4•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Comment 5•11 years ago
|
||
My OS X debug build stopped working (linking) after this change, with this error:
0:26.48 /Users/msreckovic/Repos/mozilla-central/obj-x86_64-apple-darwin13.4.0/memory/replace/logalloc/tmp40oq0x.list:
0:26.49 lock_impl_posix.o
0:26.49 FdPrintf.o
0:26.49 LogAlloc.o
0:26.49
0:26.49 Undefined symbols for architecture x86_64:
0:26.49 "mozilla::unused", referenced from:
0:26.49 FdPrintf(long, char const*, ...) in FdPrintf.o
0:26.49 ld: symbol(s) not found for architecture x86_64
0:26.49 clang: error: linker command failed with exit code 1 (use -v to see invocation)
Flags: needinfo?(n.nethercote)
You need to log in
before you can comment on or make changes to this bug.
Description
•