https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Darren Tucker changed:
What|Removed |Added
Blocks|3628|
Referenced Bugs:
https://bugzilla.mind
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Darren Tucker changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Damien Miller changed:
What|Removed |Added
Blocks|3605|3628
Referenced Bugs:
https://bugzilla.
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #11 from Darren Tucker ---
from our github CI it looks like the output format was not what I
expected and did not match the older machine I have access to here. (I
picked the way I did the workaround so it still enables it, but the
co
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Darren Tucker changed:
What|Removed |Added
Blocks||3605
--- Comment #10 from Darren Tucker
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
git...@kalvdans.no-ip.org changed:
What|Removed |Added
CC||git...@kalvdans.no-ip.org
--
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #9 from Carlo Cabrera ---
Yes, so it looks like `configure.ac` already knows to avoid
`-fzero-call-used-regs=all` when compiling with `clang-15`, except that
Apple clang uses a misleading version scheme.
Wikipedia is usually a pretty
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Michael Cho changed:
What|Removed |Added
CC||ch...@tuta.io
--- Comment #8 from Michael C
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #7 from Carlo Cabrera ---
> How do you select specific xcode versions?
You can use `xcode-select --switch /path/to/Xcode.app`. For example, to
use Xcode 14.3.1 on a GitHub macos-13 runner [1], do
```
sudo xcode-select --switch Applica
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #6 from Darren Tucker ---
(In reply to Carlo Cabrera from comment #4)
[...]
> GitHub provides free access to macOS runners for public
> repositories, and these have various versions of Xcode installed.
An interesting idea. We already
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #5 from Damien Miller ---
Darren already answered your question but fwiw I didn't suggest
--without-hardening as a workaround, but to determine whether the
compiler bug is with -Os alone or when combined with other flags.
--
You are
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #4 from Carlo Cabrera ---
> IMO you'd be better off with the compiler hardening flags rather
> than -Os. Things like -ftrapv could mitigate what would otherwise
> be a vulnerability.
Ok, sounds good. We (Homebrew) recently had to reb
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Darren Tucker changed:
What|Removed |Added
CC||dtuc...@dtucker.net
--- Comment #3 from D
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
--- Comment #2 from Carlo Cabrera ---
Yes, at Homebrew, we've also come to the conclusion that this is a
compiler bug (likely in the backend). I'll try to find the time to
report this to Apple.
Passing `--without-hardening` to `configure` also ma
https://bugzilla.mindrot.org/show_bug.cgi?id=3584
Damien Miller changed:
What|Removed |Added
CC||d...@mindrot.org
--- Comment #1 from Dami
15 matches
Mail list logo
