Bug 185997 – [Cocoa]: Remove what appears to be a stale mbmalloc target

• Status: RESOLVED
• Resolution: INVALID
• Component: bmalloc

[Joseph Pecoraro]

Remove what appears to be a stale mbmalloc target

• Attempting to build this target fails to link due to missing Foundation symbols
• It looks like the PerformanceTools/MallocBench Xcode project has a mbmalloc target which does build and work

[Joseph Pecoraro]

Created attachment 341331 [details]
[PATCH] Proposed Fix

I'm able to do things without this target... but I'll do a bit more qualification before toggling that cq flag.

[Joseph Pecoraro]

Ahh, so I see some build commands for linux ports, but I'm not sure this it actually makes sense still. Is there an advantage to the mbmalloc in bmalloc versus the mbmalloc in MallocBench? They seem to produce the same build product, so I suspect only 1 should actually be around.

[Darin Adler]

Comment on attachment 341331 [details]
[PATCH] Proposed Fix

Looks like you need to remove mbmalloc.cpp from bmalloc/CMakeLists.txt too.

There’s also some mbmalloc stuff in the WTF Xcode project.

[Joseph Pecoraro]

Apparently this is not stale. Closing the bug.

• The mbmalloc.dylib produced here uses bmalloc.
• The mbmalloc.dylib produced by MallocBench uses the system malloc.

[Geoffrey Garen]

Maybe we should clean this up by moving the mbmalloc targets from MallocBench and bmalloc into separate projects inside PerformanceTests/MallocBench. The point of mbmalloc is to be a shim around a given malloc implementation. So, you could think of it as a feature of MallocBench that it includes sub-projects that can shim around different mallocs. For example, if we wanted MallocBench to test JEMalloc or TCMalloc, we would need to write additional mbmalloc shims.