[Bug 211864] Compiler is using AVX instructions for CPUTYPE=btver1

2016-08-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211864

Kubilay Kocak  changed:

   What|Removed |Added

   Keywords||needs-qa
 CC|freebsd-amd64@FreeBSD.org   |r...@freebsd.org
Summary|[Regression] Compiler is|Compiler is using AVX
   |using AVX instructions for  |instructions for
   |CPUTYPE=btver1  |CPUTYPE=btver1
 Status|New |Open
  Flags||mfc-stable11?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"


[Bug 211864] Compiler is using AVX instructions for CPUTYPE=btver1

2016-08-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211864

Bug ID: 211864
   Summary: Compiler is using AVX instructions for CPUTYPE=btver1
   Product: Base System
   Version: 11.0-RC1
  Hardware: amd64
OS: Any
Status: New
  Keywords: regression
  Severity: Affects Some People
  Priority: ---
 Component: misc
  Assignee: freebsd-b...@freebsd.org
  Reporter: demik+free...@lostwave.net
CC: freebsd-amd64@FreeBSD.org
CC: freebsd-amd64@FreeBSD.org

Hello,

While rebuilding some ports after upgrading to 11.0-RC1 (with freebsd-update),
almost every binary is crashing with SIGILL 

The system hardware is bobcat based :
CPU: AMD C-70 APU with Radeon(tm) HD Graphics (1000.02-MHz K8-class CPU)

Bobcat CPUs have only MMX, SSE, SSE2, SSE3, SSSE3, SSE4A instructions.

Compiling without CPUTYPE results in working binaries.
With CPUTYPE=btver1, the binaries does not work, as the CPU does not have any
AVX instructions :

root@square:~ # lldb /usr/local/bin/sudo
(lldb) target create "/usr/local/bin/sudo"
Current executable set to '/usr/local/bin/sudo' (x86_64).
(lldb) run test
Process 71447 launching
Process 71447 launched: '/usr/local/bin/sudo' (x86_64)
Process 71447 stopped
* thread #1: tid = 101195, 0x000800a5421e libsudo_util.so.0`??? + 286, stop
reason = signal SIGILL: privileged instruction
frame #0: 0x000800a5421e libsudo_util.so.0`??? + 286
libsudo_util.so.0`???:
->  0x800a5421e <+286>: vzeroupper 
0x800a54221 <+289>: callq  0x800a511e4   ; symbol stub for:
sudo_debug_exit_int_v1
0x800a54226 <+294>: movq   0x20ad93(%rip), %rax  ;
libsudo_util.so.0..got + 72
0x800a5422d <+301>: movq   (%rax), %rax

Some information :

root@square:~ # uname -a
FreeBSD square 11.0-RC1 FreeBSD 11.0-RC1 #0 r303979: Fri Aug 12 02:28:24 UTC
2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

root@square:~ # cc -v
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM
3.8.0)
Target: x86_64-unknown-freebsd11.0
Thread model: posix
InstalledDir: /usr/bin

Everything was working fine while running 10.3-RELEASE

this bug might be related to this one :
https://reviews.llvm.org/D17682

Regards

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"