https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214165
Graham Perrin changed:
What|Removed |Added
Keywords|patch |
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214404
Mark Millard changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
--- Comment #19 from Mark Millard ---
(In reply to Robert Clausecker from comment #18)
https://docs.freebsd.org/en/articles/committers-guide/#archs
reports for tier 2:
QUOTE
Tier 2 platforms should be self-hosting either via the in-tree t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
--- Comment #18 from Robert Clausecker ---
(In reply to Mark Millard from comment #17)
Such a procedure requires disassembling the machine to access the storage from
another device and is thus fairly cumbersome. Last time I checked, upgra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
--- Comment #16 from Robert Clausecker ---
(In reply to Colin Percival from comment #15)
An erratum sounds reasonable. Perhaps a pointer could also be added to
updating?
--
You are receiving this mail because:
You are on the CC list for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
Colin Percival changed:
What|Removed |Added
CC||cperc...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
--- Comment #14 from Robert Clausecker ---
The only supported way to upgrade riscv64 systems is by source. You are
telling me that without hand-patching, riscv64 systems simply cannot be
upgraded. This is a sad state of affairs. Why not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
--- Comment #13 from Jessica Clarke ---
We didn't have one for 13.0->13.1. Almost nobody's seriously using RISC-V and
upgrading from source natively. For those that do they can apply the one-line
workaround.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
Robert Clausecker changed:
What|Removed |Added
CC||r...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258358
Jessica Clarke changed:
What|Removed |Added
CC||f...@freebsd.org
--- Comment #11
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247665
Jan Beich changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245067
Muhammad Moinur Rahman changed:
What|Removed |Added
Resolution|--- |Overcome By Events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252720
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
Resolution|
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261360
Yuri Victorovich changed:
What|Removed |Added
Assignee|toolchain@FreeBSD.org |y...@freebsd.org
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261360
Yuri Victorovich changed:
What|Removed |Added
Resolution|--- |Unable to Reproduce
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236344
--- Comment #11 from Mark Millard ---
(In reply to David Chisnall from comment #9)
Some of the lang/gcc* ports were taught to support
-stdlib=libc++ back in late 2022-Aug.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236344
--- Comment #10 from Lorenzo Salvadore ---
*** Bug 269110 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269645
Lorenzo Salvadore changed:
What|Removed |Added
Assignee|toolchain@FreeBSD.org |salvad...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269645
Bug ID: 269645
Summary: lang/gcc8: Remove port
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Bugzilla Automation has asked freebsd-toolchain (Nobody)
for maintainer-feedback:
Bug 269645: lang/gcc8: Remove port
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269645
--- Description ---
GCC 8 is unsupported upstream and should be removed from the ports tree.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269570
Bug ID: 269570
Summary: math/z3 fails to link with relocation R_386_TLS_LE
cannot be used with -shared
Product: Base System
Version: CURRENT
Hardware: Any
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269489
Dimitry Andric changed:
What|Removed |Added
Assignee|toolchain@FreeBSD.org |d...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269489
Jan Beich changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |toolchain@FreeBSD.org
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254
Lorenzo Salvadore changed:
What|Removed |Added
Summary|lang/gcc11: build gets |lang/gcc*: Build does not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254
Lorenzo Salvadore changed:
What|Removed |Added
CC||p5b2ea8...@t-online.de
--- Com
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244169
--- Comment #4 from Carlo Arenas ---
maybe related and therefore solved by:
https://bugs.llvm.org//show_bug.cgi?id=28629
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244169
--- Comment #3 from Carlo Arenas ---
it also doesn't replicate in FreeBSD 12.4 amd64 (using -m32 with the system
cc), so maybe should be closed?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244169
Carlo Arenas changed:
What|Removed |Added
CC||care...@gmail.com
--- Comment #2 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192686
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192686
Dimitry Andric changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #3 f
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269044
--- Comment #3 from Yuri Victorovich ---
According to the LLVM website https://llvm.org/ LLVM-16 is scheduled to be
released on Mar 7th, 2023.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269044
Yuri Victorovich changed:
What|Removed |Added
URL||https://libcxx.llvm.org/Rel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269044
--- Comment #2 from Yuri Victorovich ---
This project https://github.com/wwmm/easyeffects can't be ported because of
this issue. GCC also fails to build it because of incompatibility with
dependencies.
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269044
--- Comment #1 from Dimitry Andric ---
This was only added very recently upstream (as of 2023-01-11), in
https://github.com/llvm/llvm-project/commit/73d94b19161355d06f20678d628555719eebbdcc,
so it will be in libc++ 16. It appears to depend
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269044
Yuri Victorovich changed:
What|Removed |Added
Assignee|port...@freebsd.org |toolchain@FreeBSD.org
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268019
--- Comment #7 from Jan Beich ---
(In reply to Dimitry Andric from comment #4)
> More likely because the port has assertions disabled, so they are never hit.
> :)
I have bug 265425 applied and can't reproduce. My src.conf(5) doesn't conta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263265
Graham Perrin changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263265
Dima Panov changed:
What|Removed |Added
CC||flu...@freebsd.org
--- Comment #13 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263265
bj...@baerlin.eu changed:
What|Removed |Added
CC||bj...@baerlin.eu
--- Comment #12
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245024
--- Comment #1 from Ed Maste ---
llvm-objcopy:
--add-symbol=name=[section:]value[,flags]
Add new symbol to .symtab. Accepted flags:
global, local, weak, default, hidden, protected, file, section, object,
functi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #25 from Jessica Clarke ---
Oh arrays like that are a non-starter as you wouldn't want
vnet_offset_foo[N]... so yeah probably the interface needs reworking, not just
the implementation, if you want a "proper" approach.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #24 from Mark Johnston ---
(In reply to Jessica Clarke from comment #23)
I had tried the second suggestion, but that doesn't quite work since "n" can be
an array, as in VNET_DEFINE(struct hhook_head *,
ipsec_hhh_in[HHOOK_IPSEC_C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #23 from Jessica Clarke ---
Or you can do typedef _t vnet_type_#_n; and use that everywhere that follows so
you can use a normal tentative definition to forward-declare.
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #22 from Jessica Clarke ---
Using
__attribute__((used,section("set_vnet_entry"),alias("vnet_entry_"#_n)))
static _t vnet_alias_##_n;
as a hacky way to forward-declare the thing without the compiler complaining
seems to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #21 from Mark Johnston ---
(In reply to Jessica Clarke from comment #20)
Oh, right. So kmod_syms.awk is defeating the hack in VNET_DEFINE_STATIC. That
can be bandaged easily enough.
I tried implementing your suggestion of add
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #20 from Jessica Clarke ---
Isn't that a feature of our EXPORT_SYMS awk kmod_syms.awk | xargs -J% objcopy %
dance?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #19
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268319
Yuri Victorovich changed:
What|Removed |Added
Summary|LTO fails on the port |LTO fails on the port
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Jessica Clarke changed:
What|Removed |Added
Summary|cc_htcp(4): Setting |VNET and DPCPU defined in
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268319
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268319
Yuri Victorovich changed:
What|Removed |Added
Assignee|b...@freebsd.org|toolchain@FreeBSD.org
--
You a
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #24 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=a051e5a32dd9b36fe2b03fe152b94ee2cdce4926
commit a051e5a32dd9b36fe2b03fe152b94ee2cdce4926
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #23 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=fb398d22e6faf020957b45b43c9f6b9450c04cc9
commit fb398d22e6faf020957b45b43c9f6b9450c04cc9
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #22 from Lorenzo Salvadore ---
(In reply to Gerald Pfeifer from comment #18)
Yes Gerald, you are right. I must have copied the commands I used to re-enable
ASLR by mistake. Thanks.
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #21 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=27141421f69cb2d2bc6a462d005b251921f2c52b
commit 27141421f69cb2d2bc6a462d005b251921f2c52b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #20 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=d187c559f003650fe5eb4b9bcdc499f623d3b4a3
commit d187c559f003650fe5eb4b9bcdc499f623d3b4a3
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268021
--- Comment #5 from Mark Millard ---
(In reply to Mark Millard from comment #4)
I should not have mentioned armv6. Those still are qemu based.
FreeBSD does not support armv6 chroots or the like on aarch64
that can do such, at least withou
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268021
--- Comment #4 from Mark Millard ---
(In reply to Mark Millard from comment #3)
Going in the other direction, far less builds under
qemu on amd64 or the like so the current status is a
big, fairly recent, improvement to the armv7/v6 port
b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #19 from Gerald Pfeifer ---
Great detective work, by the way, and submitting this to LLVM upstream
definitely is the right approach.
(Patches for older GCC branches can then be submitted more easily when
something is in the GCC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #18 from Gerald Pfeifer ---
(In reply to Lorenzo Salvadore from comment #4)
> Mind that it is necessary to disable ASLR to run successfully the
> compiled binaries, which can de done with
>
> # sysctl kern.elf64.aslr.pie_enable
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268021
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268019
--- Comment #6 from Dimitry Andric ---
(In reply to Charlie Li from comment #5)
Same there, stable branches have assertions disabled. :)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268021
Yuri Victorovich changed:
What|Removed |Added
Assignee|port...@freebsd.org |toolchain@FreeBSD.org
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268019
--- Comment #5 from Charlie Li ---
https://people.freebsd.org/~vishwin/libdispatch/
The assertion (~12 years unchanged according to git-blame(1)) does not appear
to hit in the previous -STABLEs (and cut -RELEASEs) either, as they have/use
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268019
Dimitry Andric changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #4 f
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268019
--- Comment #3 from Charlie Li ---
As a data point, builds successfully with devel/llvm15, so probably a good sign
for when LLVM 15 makes it into base.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268019
Charlie Li changed:
What|Removed |Added
Assignee|b...@freebsd.org|toolchain@FreeBSD.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=b185b74b28f80aa7fbeb4122a326741211af404d
commit b185b74b28f80aa7fbeb4122a326741211af404d
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #16 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=12c4b8c968b78bcfe2532bedf26c5da31d75c60b
commit 12c4b8c968b78bcfe2532bedf26c5da31d75c60b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268009
Yuri Victorovich changed:
What|Removed |Added
URL||https://pkg-status.freebsd.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #15 from Lorenzo Salvadore ---
(In reply to Ed Maste from comment #11)
I have found the issue: I needed to merge two more of your commits. Please see
the commit message in comment #13.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #13 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=2b4f6e6f7a0b36f4592dc0058e12f55b668d6be2
commit 2b4f6e6f7a0b36f4592dc0058e12f55b668d6be2
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #14 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=7375f3899ae994888d48e099476d4a6aabf310b2
commit 7375f3899ae994888d48e099476d4a6aabf310b2
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #12 from Lorenzo Salvadore ---
Thanks Ed for you feedback. I will follow your suggestions and investigate more
deeply why my first attempt of adding
https://github.com/emaste/freebsd/commit/930a7c2ac67e1e8e511aa1d0a31a16c632060e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #11 from Ed Maste ---
> By the way, I have tried adding
> https://github.com/emaste/freebsd/commit/930a7c2ac67e1e8e511aa1d0a31a16c632060ebb
> into my patch, but it did not work. If I recall correctly, I have got an
> error 2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265809
Yuri Victorovich changed:
What|Removed |Added
Summary|clang never finishes on one |clang never finishes on one
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #10 from Ed Maste ---
> Or do you think it is better that I submit it directly to LLVM and then
> FreeBSD will merge it when it imports a new version of LLVM?
I think it is best to submit it to LLVM first and iterate on any fee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #9 from Lorenzo Salvadore ---
I have tested successfully the patch for gcc12-devel too. However, the patch
for gcc13-devel does not seem to be completely successful: the compiled binary
starts, but it stops immediately with the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
Lorenzo Salvadore changed:
What|Removed |Added
CC||d...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751
--- Comment #7 from Lorenzo Salvadore ---
Created attachment 238288
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238288&action=edit
gcc13-devel - fix sanitizer
--
You are receiving this mail because:
You are on the CC list fo
701 - 800 of 1584 matches
Mail list logo
