User Details
- User Since
- Jan 7 2014, 10:13 PM (531 w, 6 d)
Tue, Mar 12
Hm, are these files automagically pulled through a preprocessor? I wasn't aware of that... but yeah, then it is probably a good idea.
Sun, Mar 10
Fri, Mar 8
Thu, Mar 7
Mon, Mar 4
Fri, Mar 1
Sure, then I'm totally fine with this. It's better to incrementally fix the problems and then remove this option. Preferably before stable/15 gets branched :)
Is this meant as a transitional tool? Or do we expect to have some sub-Makefiles still set MK_UNDEFINED_VERSION=no because they cannot be fixed?
Thu, Feb 29
No objections from me :)
Sun, Feb 25
@devnexen_gmail.com I think you implemented https://github.com/llvm/llvm-project/commit/691b12a2dcc12fa43517d23f2a9b6039616eebc8, but the problem is that it specifcally did _not_ call elf_aux_info since that is intercepted, and might lead to segfaults.
Hmm https://github.com/llvm/llvm-project/commit/691b12a2dcc12fa43517d23f2a9b6039616eebc8 moved this function out of the file, but reverted back to calling elf_aux_info()! That was really a mistake, I'll mention that upstream.
Sat, Feb 24
Fri, Feb 23
Yeah, it's fine to test this locally but it should really be submitted upstream. If this goes through changes upstream, due to comments, it's a bit of a burden to maintain downstream.
Thu, Feb 22
Wed, Feb 21
Tue, Feb 20
Feb 17 2024
Feb 16 2024
Rename option to WITH_LLVM_FULL_DEBUGINFO, off by default.
Feb 15 2024
Maybe I should start with putting LLVM_LIMIT_DEBUGINFO in __DEFAULT_YES_OPTIONS for now? Then it would not influence most people's builds at all, but it is an easy option for those that do like full debuginfo?
Hmm... I did a test run on universe15a with MK_LLVM_LIMIT_DEBUGINFO=yes and MK_LLVM_LIMIT_DEBUG_INFO=no:
Feb 14 2024
Feb 13 2024
Feb 12 2024
Feb 11 2024
Feb 10 2024
Feb 8 2024
Feb 7 2024
Feb 5 2024
Feb 3 2024
Feb 1 2024
Jan 31 2024
Jan 30 2024
Jan 29 2024
Jan 27 2024
Jan 26 2024
Jan 25 2024
Jan 24 2024
Jan 23 2024
Jan 13 2024
Jan 12 2024
Jan 11 2024
Do we still have MIPS in 13? If so I'd like to leave it in for ease of maintenance. Do we already disable LLVM_TARGET_MIPS by default in src.opts.mk (or wherever the default is set)?