https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221423
--- Comment #6 from Mark Millard ---
(In reply to Jan Beich from comment #5)
>(In reply to Mark Millard from comment #3)
>> mix of system and gcc libraries than gcc5
>
>Tier1 and some Tier2 archs don't have system GCC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221367
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221543
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221423
--- Comment #7 from Mark Millard ---
(In reply to Mark Millard from comment #6)
Dumb typo. Wrong:
See bugzilla 221423.
Should have been:
See bugzilla 221288 .
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288
--- Comment #11 from Mark Millard ---
Trying my standard-C++ program that uses C++ threads in a more
modern context (head -r322287, lang/gcc7) in an amd64 context
under a Virtual Box virtual machine (that is running on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221423
--- Comment #9 from Mark Millard ---
Here are lang/gcc7 and system clang compile/link results as viewed
by ldd (all under head -r322287 in a Virtual Box virtual machine):
things look good until I try my threading
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221367
--- Comment #3 from Ed Maste ---
> Okay, but won't that also cause 32-bit versions of libllvm, libclang and clang
> itself to be built? We definitely don't want that. :)
Good point - I compared the result of 'make
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221543
Ed Maste changed:
What|Removed |Added
Status|New |In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221423
Gerald Pfeifer changed:
What|Removed |Added
Flags|maintainer-feedback?(gerald |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221423
--- Comment #4 from Mark Millard ---
(In reply to Mark Millard from comment #3)
You can use ldd on the a,out after each type
of link to see the different bindings.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221423
Mark Millard changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219289
Gerald Pfeifer changed:
What|Removed |Added
Blocks|219275 |
Referenced
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #9 from mikael.uran...@gmail.com ---
or you can use (untested)
CFLAGS_armv6= -fno-builtin-sincos -fno-builtin-sin -fno-builtin-cos \
-fno-builtin-sincosf -fno-builtin-sinf -fno-builtin-cosf \
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #7 from mikael.uran...@gmail.com ---
The 11 branch is missing this commit which solved the problem on 12: base
r319047
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #8 from Jason E. Hale ---
(In reply to mikael.urankar from comment #7)
Ok, I'll change it to check for less than 1200032, then. Thanks!
--
You are receiving this mail because:
You are on the CC list for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
Jason E. Hale changed:
What|Removed |Added
Flags|maintainer-feedback?(jhale@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #6 from Jason E. Hale ---
Created attachment 184300
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184300=edit
Disable unsafe-math-optimizations on armv6
This patch should disable
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
--- Comment #7 from mikael.uran...@gmail.com ---
The CFLAGS must be set globally (in make.conf), a lot of multimedia and
graphics ports are affected by this issue (on 11.0 and 11.1 at least),
12-CURRENT is not affected.
I don't think it's
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
Dirk Meyer changed:
What|Removed |Added
Status|New |In Progress
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #2 from Jan Beich ---
Err, -ffast-math is a group of flags. The issue is caused by
-funsafe-math-optimizations.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #1 from Jan Beich ---
Affected FreeBSD versions: 11.0 (clang 3.8), 11.1 (clang 4.0), 12.0
(clang500-import).
Workarounds: define USE_GCC=yes or drop -ffast-math.
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #3 from Jan Beich ---
Here's a test case:
$ cat a.c
#include
#include
int main(int argc, char *argv[])
{
printf("%Lf\n", cosl(5));
printf("%Lf\n", sinl(5));
return 0;
}
$ cc a.c -lm -O1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
Jan Beich changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
Bug ID: 220591
Summary: graphics/graphviz: fails to build on armv6 (451 ports
skipped)
Product: Ports & Packages
Version: Latest
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
Bug ID: 220590
Summary: math/fftw3: fails to build on armv6 (729 ports
skipped)
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: dinoex
Date: Tue Jul 11 08:28:44 UTC 2017
New revision: 445473
URL: https://svnweb.freebsd.org/changeset/ports/445473
Log:
- fix build on armv6
PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
Dirk Meyer changed:
What|Removed |Added
Flags|maintainer-feedback?(dinoex
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
--- Comment #3 from Jan Beich ---
Comment on attachment 184219
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184219
patch-lib-common-shapes.c
Doesn't help:
$ make
checking for sincos... no
[...]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218808
Jan Beich changed:
What|Removed |Added
Blocks||214864
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
mikael.uran...@gmail.com changed:
What|Removed |Added
CC||mikael.uran...@gmail.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
--- Comment #5 from mikael.uran...@gmail.com ---
We build package for 11.0 on armv6 now?
--
You are receiving this mail because:
You are on the CC list for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
mikael.uran...@gmail.com changed:
What|Removed |Added
CC||mikael.uran...@gmail.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
--- Comment #5 from Jan Beich ---
(In reply to mikael.urankar from comment #4)
> Are you sure 12 is affected?
Ah, you're right! When writing comment 1 I've only checked whether sincos is
emitted but not if libm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Jan Beich changed:
What|Removed |Added
Flags|
Jan Beich has asked freebsd-toolchain@FreeBSD.org for
maintainer-feedback:
Bug 219484: cad/openvsp: fails to build with lang/gcc6 or later on 10.*
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #2 from Jan Beich ---
(In reply to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Dimitry Andric changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Jan Beich changed:
What|Removed |Added
Summary|cad/openvsp: fails to build |cad/openvsp: fails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #6 from commit-h...@freebsd.org ---
A commit references this bug:
Author: dim
Date: Wed Jul 19 18:22:32 UTC 2017
New revision: 321222
URL: https://svnweb.freebsd.org/changeset/base/321222
Log:
Pull in r229281 from upstream
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #4 from Gerald Pfeifer ---
(In reply to Jan Beich from comment #2)
> Alternatives are locking the ports to USE_GCC < 6 (if gerald is OK)
> or laying on BROKEN_FreeBSD_10 deathbed.
I prefer the latter,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #8 from fernando.apesteg...@gmail.com ---
(In reply to Jan Beich from comment #7)
Thanks for testing. I wonder, how ofter are snapshots of -STABLE created? I
couldn't find any new enough to test the port with poudriere:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220883
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220883
Dimitry Andric changed:
What|Removed |Added
Assignee|freebsd-toolchain@FreeBSD.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218808
--- Comment #6 from Jan Beich ---
lld 5.0 per base r321369 does support --warn-unresolved-symbols, so comment 1
shows the following:
/usr/bin/ld.lld: warning: undefined symbol: environ
>>> referenced by a.c
>>>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #12 from fernando.apesteg...@gmail.com ---
(In reply to Kubilay Kocak from comment #11)
Having a look at the error log, it seems the missing operator is used in libc++
itself (~basic_stringbug()). With GCC < 6, the compiler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Gerald Pfeifer changed:
What|Removed |Added
Status|New |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #9 from fernando.apesteg...@gmail.com ---
Does this PR need additional action on my side in order to be closed?
--
You are receiving this mail because:
You are on the CC list 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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Kubilay Kocak changed:
What|Removed |Added
Resolution|FIXED |---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Bug 219484 depends on bug 220951, which changed state.
Bug 220951 Summary: cad/openvsp: Update to 3.13.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220951
What|Removed |Added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218808
O. Hartmann changed:
What|Removed |Added
Summary|www/firefox: usr/bin/ld:|www/firefox:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
fernando.apesteg...@gmail.com changed:
What|Removed |Added
Depends on||220951
Referenced
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218808
--- Comment #7 from O. Hartmann ---
(In reply to Jan Beich from comment #6)
I "solved" those problems for now by not usinf LLD as LD for the time being it
is still harmful.
Thanks.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #5 from Dimitry Andric ---
I'll merge libc++ r229281 into stable/10 later today, at least it'll appear in
10.4-RELEASE then. Jan, is it worth bumping __FreeBSD_version for this?
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218808
--- Comment #3 from O. Hartmann ---
(In reply to Jan Beich from comment #2)
Is there a solution? www/firefox doesn't build on 12-CURRENT (recent, as of
today) anymore if WITH_LLD_IS_LD is enabled.
poudriere also
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214971
Ed Maste changed:
What|Removed |Added
Status|In Progress |Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217648
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218861
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218860
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Kubilay Kocak changed:
What|Removed |Added
Flags|merge-quarterly-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #20 from commit-h...@freebsd.org ---
A commit references this bug:
Author: rakuco
Date: Fri Jul 28 21:45:45 UTC 2017
New revision: 446855
URL: https://svnweb.freebsd.org/changeset/ports/446855
Log:
Explicitly build with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
fernando.apesteg...@gmail.com changed:
What|Removed |Added
Attachment #184778|0 |1
is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Raphael Kubo da Costa changed:
What|Removed |Added
Status|Open|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288
--- Comment #9 from Mark Millard ---
(In reply to Mark Millard from comment #6)
Returning to a g++6 based a.out back trace
for the C++ threading to show some
infrastructure usage involved:
Thread 12 received signal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
Kubilay Kocak changed:
What|Removed |Added
Resolution|FIXED |---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220590
Jan Beich changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220591
Jan Beich changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288
--- Comment #5 from Mark Millard ---
I suspect this mix of infrastructures ties in to
why standard c++ threading fails under the likes
of g++6 compiles while the code works when compiled
and linked via system clang++
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288
--- Comment #6 from Mark Millard ---
(In reply to Mark Millard from comment #5)
To avoid confusion from a typing/editing
error. . .
"Note #3 -> #4 goes from" in the reference
to the g++6 based a.out backtrace should
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288
--- Comment #7 from Mark Millard ---
(In reply to Mark Millard from comment #5)
FYI: An older report of the threading issues
with the tiny program:
static void f() {}
int main(int, const char* [])
{
auto a0{
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221288
--- Comment #8 from Mark Millard ---
(In reply to Mark Millard from comment #7)
Looking at its details bugzilla 212330 is not
a good example for here in 221288. For one the
failing context was armv6 and amd64 worked.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
--- Comment #16 from fernando.apesteg...@gmail.com ---
Comment on attachment 184778
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184778
patch to the ports tree
Is this patch acceptable?
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219484
fernando.apesteg...@gmail.com changed:
What|Removed |Added
Attachment #184778|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221733
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221733
Ed Maste changed:
What|Removed |Added
Status|New |Open
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221588
Conrad Meyer changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221588
--- Comment #2 from Dimitry Andric ---
So what this test case causes is:
fatal error: error in backend: No open frame
This happens with most versions of clang that I could test, and is due to the
following inline
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219289
Bug ID: 219289
Summary: security/clambc: fails to build with lang/gcc6 or
later
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #14 from Mark Millard ---
(In reply to John Baldwin from comment #8)
With the following hacks I've been able to get
an output for the debug.minidump=0 based
vmcore.2 (2 GiBYte RAM dumped) for
powerpc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216080
Jan Beich changed:
What|Removed |Added
Blocks|219275 |
Referenced
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219289
--- Comment #2 from Gerald Pfeifer ---
Should we then just deprecate and remove this port? It appears we've
got way too much old cruft in the tree... :-(
--
You are receiving this mail because:
You are on the CC list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219289
--- Comment #3 from Dimitry Andric ---
Certainly, for a security product, it is a little strange they have not updated
their backend libraries for 6 years. I would not trust this, in any case. :)
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #8 from John Baldwin ---
Can you pop up to frame 13 (solib_svr4_r_map) and 'p *info' and 'p *lmo'? The
lack of working exceptions from clang (which appears to be the source of the
coredump in gdb itself)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #10 from Mark Millard ---
(In reply to John Baldwin from comment #8)
The bt that I included shows libstdc++ in use
inside /usr/local/bin/gdb, not libc++ . This
is because /usr/local/bin/gdb was built under
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #9 from Mark Millard ---
(In reply to John Baldwin from comment #5)
As for ps -M /var/crash/vmcore.7 listing no
processes:
main uses kvm_getprocs, which in turn eventually
does:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #6 from Mark Millard ---
(In reply to John Baldwin from comment #5)
I've used both gdb's as well but I've had more
occasions when system's gdb worked and ports
did not than the other way around (when there
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #5 from John Baldwin ---
I would start with trying to debug why 'ps -M' doesn't work by stepping through
'ps'.
In terms of gdb7 vs gdb6, I definitely used gdb7 on userland binaries with
threads, fork
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #2 from Mark Millard ---
(In reply to John Baldwin from comment #1)
The ps -M result for using:
# svnlite diff /usr/src/lib
Index: /usr/src/lib/libkvm/kvm_private.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #12 from Mark Millard ---
(In reply to Mark Millard from comment #11)
So trying:
ps -M /var/crash/vmcore.2 -N /usr/lib/debug/boot/kernel/kernel.debug
for a vmcore.2 based on: debug.minidump=0
things do
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #13 from Mark Millard ---
(In reply to Mark Millard from comment #12)
I found the "Raw core file not supported"
logic in /usr/src/lib/libkvm/kvm_powerpc.c :
static int
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #11 from Mark Millard ---
(In reply to Mark Millard from comment #9)
[This note is limited to contexts with gcc
4.2.1 based kernels.]
Summary after avoiding a user error: looks
like there is a default of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #3 from Mark Millard ---
(In reply to Mark Millard from comment #2)
An FYI based on my ET_DYN test hack in
libkvm:
I've gotten some more panics with the libkvm
change in place. This makes the new
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #4 from Mark Millard ---
A not as libkvm tied note about which gdb
works better for 32-bit powerpc in at
least some contexts:
I took an a.out (from clang++
targeting powerpc) and tried
/usr/local/bin/gdb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #7 from Mark Millard ---
(In reply to John Baldwin from comment #5)
This note is for the /usr/local/bin/gdb crash.
As for building ports with debug information, I use
as a default context:
# svnlite diff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220184
O. Hartmann changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220184
--- Comment #10 from Conrad Meyer ---
If overheating of the CPU is causing segfaults (non-overclocked), your CPU is
already damaged. Some stress test like Prime95 or IntelBurnTest should also
reproduce the issue.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220184
--- Comment #11 from Chris Collins ---
Have now tested on an old laptop (slow hardware so long waiting time)
It has the exact same symptons.
Stable when building 11.0 or 10.3 on older clang.
Once on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220184
--- Comment #12 from Chris Collins ---
(In reply to Conrad Meyer from comment #10)
it has no issue with prime95 stress tests and other stress tests.
So to confirm absolutely 100% stable in every software on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220184
--- Comment #17 from Chris Collins ---
Perhaps buildworld with clang 4.0 is now the ultimate hardware stability test
:)
3rd compile was fine, now running 4th.
Will still test on the server class hardware this
301 - 400 of 2078 matches
Mail list logo