- User Since
- Jul 1 2014, 6:02 PM (267 w, 5 d)
- Always follow the allocated path, don't free prematurely.
Sat, Aug 17
Fri, Aug 16
Thu, Aug 15
Fri, Aug 9
I've fixed the expression to exclude gcc < 8 and tested on amd64 and riscv.
- Use the correct expression to add -Wno-class-memaccess.
I completely misunderstood what was going on. The in .. excludes gcc 4.2.1 and this is a gcc 8.0+ warning. The incorrect copy and paste meant it worked by accident for 6.4. I'm testing a new version now...
Thu, Aug 8
This is breaking the xtoolchain CI jobs https://ci.freebsd.org/job/FreeBSD-head-amd64-gcc/10997/
Wed, Aug 7
Mon, Aug 5
Fri, Aug 2
Thu, Aug 1
Wed, Jul 31
Tue, Jul 30
Mon, Jul 29
Why is a shim required? All arguments are extended to 64-bits as part of the combat layer. There would be an issue if len were an off_t, but it's a size_t. The only pointers point to off_t's which are always 64-bit and thus require no special handling.
Fri, Jul 26
Thu, Jul 25
Wed, Jul 24
This looks like it provides a viable update path. As you say, libc may have some edge case issues, but it does look like it does the job of letting people upgrade without a reinstall from media. What do you think about about timing this change? It seems like it should happen close to the ELFv2 switch so people get the whole thing out of the way at once.
- Detect old auxargs constant and translate them (from bdragon@).
- Put freebsd_fixup_old_auxargs under #ifdef powerpc.
Tue, Jul 23
OK, I wasn't sure exactly how the bits in rtld were going to go. It doesn't look like this is going to be as much help as I'd hoped.
- Use the correct AT_COUNT value, not the CheriBSD one.
Mon, Jul 22
Did you apply a manual bump of __FreeBSD_version and P_OSREL_POWERPC_NEW_AUX_ARGS? That part of the patch is now out of date.
Jul 19 2019
I found this in our CheriBSD diffs. I'm not sure how @arichardson ran into it.
Jul 18 2019
Jul 17 2019
Jul 16 2019
NetBSD just committed these changes and some others just now. I'm waiting for cvsweb to update so I can check what was actually committed.
Submitted upstream: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=54382
Jul 15 2019
While we should probably just do in amd, these are easy fixes and there's no upstream conflicts to worry about (last am-utils release in 2014 and their git server don't seem to host a repo.
Jul 11 2019
Jul 9 2019
It seems deeply weird that a program would set these flags with mprotect, but this change seems fine (modulo changing the error to EINVAL).
Jul 3 2019
Jul 2 2019
- Call __sys_nmount from the mount wrapper.
Jun 28 2019