In D17917#382796, @jack_gandi.net wrote:In D17917#382778, @pfg wrote:Maybe a sweep with opengrok is a good idea to see where we should be using this.
I don't know about opengrok, but this is a new feature only affecting a small part of the ABI so it seems pretty well contained.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Nov 9 2018
Nov 9 2018
In D17903#382777, @bapt wrote:In D17903#382776, @pfg wrote:For the record ...
We really do need to update libedit (from NetBSD).
These changes are welcome but I fear the approach of trying to preserve our changes is not sustainable anymoreSomeone brave, and with time, has to take the step of just bringing the NetBSD version ...
I did it once, it is not that hard, and our version right now is not that far from there version is it? for the record, I have also contacted christos@ by email so he can wait on this review.
Maybe a sweep with opengrok is a good idea to see where we should be using this.
For the record ...
Nov 1 2018
Nov 1 2018
Oct 8 2018
Oct 8 2018
LGTM.
(I currently don't have the time to go over to Release Engineering for this though ::-/ )
Sep 17 2018
Sep 17 2018
Sep 9 2018
Sep 9 2018
pfg added a comment to D17083: Alter the prototype of qsort_r(3) to match POSIX, which adopted the glibc-based interface..
In D17083#364265, @pfg wrote:This is likely to cause huge havoc in the ports tree: we created the API and Apple adopted it. Later glibc and NetBSD adopted their own variant.
Sep 8 2018
Sep 8 2018
pfg added a comment to D17083: Alter the prototype of qsort_r(3) to match POSIX, which adopted the glibc-based interface..
This is likely to cause huge havoc in the ports tree: we created the API and Apple adopted it. Later glibc and NetBSD adopted their own variant.
Aug 22 2018
Aug 22 2018
MFC r337728: (committed by jilles)
Aug 21 2018
Aug 21 2018
libthr: minor spacing cleanup.
Aug 18 2018
Aug 18 2018
In D16722#356962, @kib wrote:In D16722#356907, @pfg wrote:
POSIX compliance improvements in the pthread(3) functions.
In D16722#356897, @kib wrote:I do not think that functions definitions need to use __restrict. libthr is compiled only with C99 compiler, never C89 nor C++, so direct use of the restrict keyword is fine.
Aug 17 2018
Aug 17 2018
In D16722#356695, @kib wrote:In D16722#356631, @pfg wrote:
Checked for compliance against POSIX/SUSv4-2018.
Document the changes in the man pages.
In D16722#356491, @kib wrote:In D16722#356448, @pfg wrote:In D16722#356440, @kib wrote:Did you verified include/pthread.h against POSIX/SUSv4-2018 ?
No, I only checked individual functions against the public v2-1997, which came up first in my search.
It does not matter much which version of POSIX you used. I am concerned with the header change to match at least some standard.
Avoid const poisoning the private functions by using __DECONST early.
In D16722#356440, @kib wrote:Did you verified include/pthread.h against POSIX/SUSv4-2018 ?
Aug 16 2018
Aug 16 2018
Aug 15 2018
Aug 15 2018
Drop the bogus umtx change: instead adopt a couple of __DECONST() in
libthr to workaround the warnings.
May I suggest you add "test" targets to the ports?
Aug 14 2018
Aug 14 2018
Aug 9 2018
Aug 9 2018
pfg accepted D13528: fuse extattrs: fix issue when neither uio nor size were not passed to VOP_* (logic only)..
(I thought this had been committed already :-/ )
Aug 8 2018
Aug 8 2018
Fix printf(1) ignores width and precision in %b format.
Revert r337440: the log message is wrong.
msdosfs: fixes for Undefined Behavior.
Aug 7 2018
Aug 7 2018
Fix printf(1) ignores width and precision in %b format.
libc: fix cases of undefined behavior.
sed(1): partial fix for the case of the regex delimited with '['.
Aug 6 2018
Aug 6 2018
Jul 30 2018
Jul 30 2018
sed: compile with the default WARNS level.
sed: unsign some indexes to fix sign-compare warnings.
Jul 29 2018
Jul 29 2018
I think you still have to fix the shebang on "configure".
Cool thanks! Please try to upstream the changes when you can.
Jul 18 2018
Jul 18 2018
Jul 17 2018
Jul 17 2018
Document FreeBSD version 1200074.
FreeBSD_version bump as per r336351,
Jul 16 2018
Jul 16 2018
Update libstdc++ configuration.
Jul 9 2018
Jul 9 2018
localedef(1): remove duplicated includes.
sed(1): Suppress implicit-fallthrough.
Thanks! feel free to MFC my previous change.
Jul 8 2018
Jul 8 2018
libiconv: correct undefined behavior.
gzip: fix for undefined behavior.
Jul 3 2018
Jul 3 2018
Abandon: it does seem like we can just remove libssp but I don't have time to dig deeper.
Jun 30 2018
Jun 30 2018
In D15687#340722, @kib wrote:In D15687#340721, @pfg wrote:In D15687#340720, @kib wrote:In D15687#340719, @pfg wrote:In D15687#340718, @kib wrote:I fail to understand this. What is built instead of libssp when MK_GCC is NO ? If the answer is nothing, then you get non-functional system.
The answer is indeed nothing. Why is the system non-functional? Why do we need libssp and is there documentation to replace it?
Because you need to satisfy the ssp symbols to get working binaries.
So what is the point of this patch ?
The point is that libssp is part of GCC so we need to know what we need to replace it with (without looking insidie since its GPLd).
I am even more confused now. Why did not you answered this question for yourself before even proposing to remove libssp by the switch ?
Well, that was the question I was asking myself. I moved libssp along with the other libgcc libs (where it came from) and buildworld still works, I get no missing symbols anywhere.
I theorized that we appear to have added the FORTIFY_SOURCE functions but we are not using them anywhere.Ports are working still on my machine (11-stable), after building without libssp:
file /usr/lib/libssp_nonshared.a: /usr/lib/libssp_nonshared.a:: cannot open `/usr/lib/libssp_nonshared.a:' (No such file or directory)Goal is to have the functional system, and to have it GPL-free is somewhere in the second line.
Yes, I am just trying to identify why current is non-functional without the GPL'd piece.
If you do not provide libssp(_nonshared.a), then you should disable -f option for ssp, which is probably enabled by default in the spec for gcc, and somewhere in c++ for clang.
Thanks, that is a good hint.
In D15687#340720, @kib wrote:In D15687#340719, @pfg wrote:In D15687#340718, @kib wrote:I fail to understand this. What is built instead of libssp when MK_GCC is NO ? If the answer is nothing, then you get non-functional system.
The answer is indeed nothing. Why is the system non-functional? Why do we need libssp and is there documentation to replace it?
Because you need to satisfy the ssp symbols to get working binaries.
So what is the point of this patch ?
The point is that libssp is part of GCC so we need to know what we need to replace it with (without looking insidie since its GPLd).
I am even more confused now. Why did not you answered this question for yourself before even proposing to remove libssp by the switch ?
In D15687#340718, @kib wrote:I fail to understand this. What is built instead of libssp when MK_GCC is NO ? If the answer is nothing, then you get non-functional system.
In D15687#340674, @antoine wrote:All ports fail to build with this patch
Jun 26 2018
Jun 26 2018
In D15687#339170, @emaste wrote:For reference, BSDL __stack_chk_fail in Android https://android.googlesource.com/platform/bionic/+/ics-mr1-release/libc/bionic/ssp.c and NetBSD http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/misc/stack_protector.c?annotate=1.9&only_with_tag=MAIN.
The libssp subdir should be added only if both MK_SSP and MK_GCC are true; someone who sets WITHOUT_SSP but WITH_GCC should not get it. Also, it seems there are other MK_SSP conditionals that need to be investigated in other Makefiles and share/mk.
In D15687#339162, @brooks wrote:In terms of exposed symbols (see objdump -T), libssp definitely is a FORTIFY_SOURCE implementation. I've not looked at the code to avoid contamination in case we need a cleanroom one.
For the record: the compiler libssp is not the same as libssp as in NetBSD and bionic's libc, which implements the libc support for FORTIFY_SOURCE.
Jun 13 2018
Jun 13 2018
As a sidenote: one file in bhyve has no license. This is a problem.
I agree with other reviewers: The SPDX changes should be split.
Jun 11 2018
Jun 11 2018
style(9): Fix tabs after #define.
Jun 7 2018
Jun 7 2018
Jun 6 2018
Jun 6 2018
May 14 2018
May 14 2018
May 12 2018
May 12 2018
Looks good to me
May 6 2018
May 6 2018
pfg committed rS333311: msdosfs: use vfs_timestamp() to generate timestamps instead of getnanotime()..
msdosfs: use vfs_timestamp() to generate timestamps instead of getnanotime().
pfg removed a reviewer for D15297: msdosfs: use vfs_timestamp() to generate timestamps instead of getnanotime(): emaste.
For the record, his patch first appeared in PR 217560, it's unrelated to the Bug, so I asked for an independent CR.
I will take care of it.
May 4 2018
May 4 2018
Approved.
Hoping someone else can do the honors though .. I did somethig dumb with my partition table.
msdosfs: long names of files are created incorrectly.
Apr 28 2018
Apr 28 2018
Apr 25 2018
Apr 25 2018
pfg committed rS332986: makefs: Use ENODATA instead of ENOMSG as a translation for missing ENOATTR..
makefs: Use ENODATA instead of ENOMSG as a translation for missing ENOATTR.
Apr 19 2018
Apr 19 2018
Apr 8 2018
Apr 8 2018
Apr 4 2018
Apr 4 2018
pthread.h: minor indentation cleanups.
pthread.h: drop nullability attributes.
Mar 20 2018
Mar 20 2018
There is little interest on this.
Mar 6 2018
Mar 6 2018
math/R-cran-truncnorm: Update to 1.0-8
Feb 28 2018
Feb 28 2018
Feb 23 2018
Feb 23 2018
math/reduce: update to latest snapshot and cleanup.