summaryrefslogtreecommitdiffstats
path: root/gnu/usr.bin (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* not renaming those temp files should be fatalespie2019-12-172-2/+10
| | | | | | | this got fixed in recent binutils, but it's GPLv3. So do the same thing in a slightly different way okay guenther@
* Like Targets.def include AMDGPU lines in generated .def files forjsg2019-12-061-4/+7
| | | | | | | AsmParsers.def AsmPrinters.def and Disassemblers.def. Required so that LLVM headers will have prototypes for LLVMInitializeAMDGPUAsmPrinter() and LLVMInitializeAMDGPUAsmParser().
* In lldb, use a OpenBSD signal map instead of leveraging the FreeBSD one.mortimer2019-11-271-1/+2
| | | | ok kettenis@
* Revert previous "honour DEBUG", otherwise clang uses -g resulting in hugesthen2019-11-261-1/+2
| | | | | | | | | | | | | | | | objects and it running out of memory in the "building shared LLVM library" stage (at least on i386). building standard LLVM library building shared LLVM library (version 1.0) cc -shared -Wl,-soname,libLLVM.so.1.0 -fpic -o libLLVM.so.1.0 `echo AMDGPUAsmParser.so AMDGPUInstPrinter.so AMDGPUAliasAnalysis.so AMDGPUAlwaysInlinePass.so AMDGPUAnnotateKernelFeatures.so AMDGPUAnnotateUniformValues.so AMDGPUArgumentUsageInfo.so [...snip lots of .so...] ThinLTOBitcodeWriter.so WholeProgramDevirt.so | tr ' ' '\n' | sort -R` -Wl,--start-group -Wl,--end-group LLVM ERROR: out of memory cc: error: unable to execute command: Abort trap cc: error: linker command failed due to signal (use -v to see invocation) ar: libLLVM.a: No space left on device *** Error 1 in gnu/usr.bin/clang/libLLVM (<bsd.lib.mk>:193 'libLLVM.a': @ar cqD libLLVM.a `lorder AMDGPUAsmParser.o AMDGPUIn stPrinter.o AMDG...) *** Error 254 (<bsd.lib.mk>:225 'libLLVM.so.1.0')
* Honour DEBUGkn2019-11-251-2/+1
| | | | OK mortimer
* Add lldb support for debugging running binaries on amd64.mortimer2019-11-093-3/+95
| | | | | | | Follows a similar model as NetBSD. Much help from patrick, kettenis and guenther. lldb and lldb-server remain not installed by default. ok patrick@
* Silence the compiler on 64bits archs where sizeof(void *) != sizeof(int).mpi2019-11-081-1/+1
| | | | ok partrick@, kettenis@
* Add retguard for octeon/mips64.mortimer2019-10-252-3/+5
| | | | | | | | | | For this architecture we use separate retguard prologue and epilogue code for static or PIC code. In the PIC case we use some additional code before the retguard epilogue to recover the function start address and the GOT pointer in order to get the per-function random cookie. Much thanks to visa@ for suggestions and advice making it all work. ok deraadt@ visa@
* Fix backtrace across signals on amd64kurt2019-10-211-13/+23
| | | | okay guenther@ kettenis@
* Update clang build infrastructure for LLVM 8.0.1.patrick2019-09-016-14/+14
|
* Various fixes to make this compile with clang on powerpc.kettenis2019-08-117-13/+19
| | | | ok visa@
* Remove extra =back from OpenBSD::Pledge PODafresh12019-07-241-3/+1
| | | | From Edgar Pettijohn <edgar () pettijohn-web ! com>
* Install OpenBSD::Unveil.3p manpageafresh12019-07-141-0/+1
| | | | Reminded by brynet@
* Compile clang with -fomit-frame-pointer on mips64. This releases thevisa2019-07-111-1/+6
| | | | | | | | | | frame pointer for better use and lets the compiler run a little faster. The resulting compiler binary is a half bit smaller too. Note that frame pointer elimination is not applicable everywhere. mips64 has the tooling that allow its use in this case. OK kettenis@
* Put OpenBSD::Unveil in perl MANIFESTafresh12019-07-101-0/+3
|
* Add OpenBSD::Unveil, a perl interface to unveil(2)afresh12019-07-093-0/+285
| | | | OK brynet@, bluhm@
* Fix Makemaker manpage section detectionafresh12019-07-061-2/+19
| | | | | | | | This patch sets the section in perl manpages to "3p" instead of "3" which should be less confusing as you do find them in section 3p on OpenBSD. Initial idea and OK espie@, makes sense to schwarze@
* Update clang build infrastructure for LLVM 8.0.0.patrick2019-06-2362-152/+259
|
* Delete totally bogus code specifically targetted at mandocschwarze2019-06-141-7/+0
| | | | | | | | | | | | | | which tried to figure out whether mandoc supported UTF-8 output (which it has been doing since 2011) and which passed the -T locale option (which has been the default since 2014 and always will) but which required the -V option to work (which was deleted half a decade ago and will not come back). Nowadays, it is safe to assume that mandoc just works with UTF-8 on both the input and output sides - in literally each and every operating system providing a mandoc port or package, even those that are seriously lagging behind. This patch will also be pushed upstream. OK tb@
* Reapply patches lost in the perl 5.28.2 updateafresh12019-06-061-1/+10
|
* fix core dump reported by Adam Thomson; ok tb@otto2019-05-272-3/+5
|
* Install the new perldelta as man pagesafresh12019-05-251-0/+2
|
* Update to perl 5.28.2afresh12019-05-2477-505/+2011
| | | | | | | Minor bugfixes and documentation improvments. See perldelta for details. https://metacpan.org/pod/release/SHAY/perl-5.28.2/pod/perldelta.pod OK bluhm@
* stop using the moribund MLINKS bsd.man.mk feature;schwarze2019-05-171-2/+4
| | | | | no functional change intended; OK patrick@
* stop using the moribund MLINKS bsd.man.mk feature;schwarze2019-05-171-2/+3
| | | | | no functional change intended; OK millert@
* Stop using the moribund MLINKS bsd.man.mk feature for Perl manuals.schwarze2019-05-161-14/+0
| | | | | | | | It was only used in a very unsystematic way for a small minority of Perl manual pages anyway, and using it consistently would entail unsustainable maintenance workload. Using input from afresh1@ espie@ and Grinnz#p5p; OK afresh1@ espie@ jmc@.
* Stop using the moribund MLINKS bsd.man.mk feature for clang(1).schwarze2019-05-162-8/+9
| | | | | Patch clang.rst such that "gmake -f Makefile.sphinx man" keeps working. Using input from jsg@; OK patrick@; "no worries" deraadt@
* The perldoc(1) program wants to support the MANWIDTH environmentschwarze2019-05-051-0/+4
| | | | | | | | | | | variable and fall back to what stty(1) reports, and it does so with nroff(1), but it didn't with mandoc(1) because it didn't know how to pass the desired width to mandoc. Teach it to use "-O width=". OK afresh1@. I noticed the unimplemented feature when Andrew Daugherity asked on tech@ what the point of a certain patch in FreeBSD is (which it turns out we don't need).
* Like we already do for pod2man(1), always let perldoc(1) produce man(7)schwarze2019-05-051-1/+3
| | | | | | | | | | | output in UTF-8 encoding on OpenBSD. The consumer is always mandoc(1) on OpenBSD, which can always handle UTF-8 input (no matter what LC_CTYPE is) and which always produces useful output: UTF-8 for LC_CTYPE=*.UTF-8 or ASCII otherwise, in particular for LC_CTYPE=C. Patch written after afresh1@ reported that "perldoc -oman" output looked bad in both output modes. OK afresh1@.
* Fix Pod::Perldoc::ToMan and use it as the default perldoc formatterafresh12019-05-042-0/+5
| | | | | | From Andrew Daugherity <andrew.daugherity () gmail ! com> Corrections to fix and OK millert@, suggestions and OK schwarze@
* On powerpc, link with -Wl,-relax as clang is a monster and code exceeds thekettenis2019-04-191-1/+10
| | | | | | | | | maximum reachability of the PowerPC branch instructions. Also override NOPIE_FLAGS to avoid building code with -fno-pie as doing so is incompatible with secure-plt when using clang as the compiler. ok visa@, guenther@
* Use literals as format strings. This fixes an error reported by clang.visa2019-04-151-2/+2
| | | | OK deraadt@ millert@ kettenis@
* Add a type cast to silence clang error about an implicit conversionvisa2019-04-151-1/+1
| | | | | | from unsigned long to int. OK deraadt@ millert@ kettenis@
* mortimer unlinked libobjc from the build, but didn't know how to cvs rm.tedu2019-04-032-82/+0
| | | | | I don't know much about compilers, but what I do have are a very particular set of skills. Skills I have acquired over a very long career.
* Do not install libLLVM.a. At present the clang tools are eitherderaadt2019-04-021-0/+1
| | | | | | static-linked against private copy, or dynamic tools against the *.so, or ports use independent componented versions. Saves ~85MB in /usr. ok jsg
* When linking libLLVM.a in clang and lld include it within thejsg2019-03-063-15/+10
| | | | | ld --start-group --end-group block. bfd ld seems to need this where lld doesn't.
* Define LLVM_NATIVE_* in llvm-config.h like the result of a cmakejsg2019-03-063-41/+12
| | | | | | | | | build so external users of Support/TargetSelect.h will work correctly. Previously these were defined via -D in CPPFLAGS. Fixes llvmpipe erroring out due to no targets being registered. ok patrick@
* Allow make obj in libLLVM to succeed on non-LLVM architectures bypatrick2019-03-051-0/+4
| | | | | | | making sure LLVM_ARCH is set before including architecture-specific Makefiles. ok deraadt@
* add llvm-config.1 from llvm-config.rstjsg2019-03-052-2/+210
| | | | | Generated with gmake and py-sphinx installed via cd /usr/src/gnu/llvm/docs && gmake -f Makefile.sphinx man
* Build and install a shared libLLVM, llvm-config and llvm includes.jsg2019-03-0595-964/+460
| | | | | | This is required to build the radeonsi Mesa driver. ok patrick@
* build AMDGPU Target in addition to nativejsg2019-03-053-8/+10
|
* add Makefile for llvm-configjsg2019-03-058-0/+658
| | | | | | A build time dependency on python is avoided by generating the arch specific list of library components in advance. A 'reconf' target is included to regenerate them. Approach discussed with patrick@
* Fix a crash: don't assume that all input files are ELF objectsjca2019-03-011-2/+7
| | | | | | | | | | | | ld(1) would try to free uninitialized memory when used with -r -b binary <fontfile> by ports/textproc/mupdf. Perform the same bfd type check as bfd_elf_match_symbols_in_sections(). Fix found the hard way, cheese and wine sponsor: miod. Almost identical fix already present upstream. Also set the freed pointer to NULL, just in case. ok tb@ sthen@
* In preparation for reusing libLLVM component library Makefiles to buildjsg2019-02-2613-29/+100
| | | | | | | | libLLVM from a single directory avoid reused filenames by symlinking duplicated names with a prefix of the component library name so object file names will be unique. symlink approach suggested by deraadt@ ok patrick@
* define LLVM_ENABLE_THREADS and LLVM_HAS_ATOMICSjsg2019-02-261-2/+2
| | | | | | matches the result of building with cmake ok patrick@
* add sources matching unresolved symbols seen using Mesa with libLLVMjsg2019-02-256-7/+16
| | | | ok patrick@
* Remove -S from install commandskn2019-02-244-8/+8
| | | | | | | | As of usr.bin/xinstall/install.c revision 1.68, -S is a no-op and install(1) will always create files safely, thus clean the option usage from the tree. Diff from Lauri Tirkkonen <lotheac at iki dot fi>, thanks.
* When bsd.lib.mk builds shared libraries it builds with -DPIC whichjsg2019-02-141-0/+12
| | | | | | | | | | | | | | | causes problems in the following files which use PIC as a variable name. Undefine PIC in llvm-config.h to minimise the diff to upstream LLVM. include/llvm/MC/MCObjectFileInfo.h lib/MC/MCObjectFileInfo.cpp lib/Transforms/Scalar/LICM.cpp lib/Transforms/Utils/PredicateInfo.cpp These are the files that would be built as part of a shared libLLVM. There are other files with PIC variable names in clang code. #undef PIC approach suggested by kettenis@
* Apply pre-built unicore patch, remove excess files - perl-5.28.1afresh12019-02-13491-131525/+161528
| | | | looking good sthen@, Great! bluhm@
* Apply local patches, remove excess files - perl-5.28.1afresh12019-02-1354-596/+493
| | | | looking good sthen@, Great! bluhm@