Re: gcc 4.2 miscompilation with -O2 -fno-omit-frame-pointer on amd64

2011-12-08 Thread Rafal Jaworowski
On 2011-12-07, at 21:28, Arnaud Lacombe wrote: Hi, On Sat, Nov 19, 2011 at 5:01 AM, Gleb Kurtsou gleb.kurt...@gmail.com wrote: Hi, I was lucky to write a bit of code which gcc 4.2 fails to compile correctly with -O2. Too keep long story short the code fails for gcc from base system and

Re: gcc 4.2 miscompilation with -O2 -fno-omit-frame-pointer on amd64

2011-12-08 Thread Gleb Kurtsou
On (08/12/2011 10:01), Piotr Nowak wrote: We're working on PowerPC target using GCC 4.2.1 and FreeBSD 6.1. It seems like we have similar problem. In our case GCC sometimes very unfortunately optimize code with -fno-omit-frame-pointer. Example shown below covers file sys/powerc/booke/pmap.c

Re: [SOLVED]Re: 64bit build errors - use gcc46

2011-12-08 Thread Tom Evans
On Thu, Dec 8, 2011 at 6:05 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au wrote: Just to let the list know, I changed as - ./configure --as=/usr/local/bin/as. I still had the exact same error oddly enough. I then had to install gcc46; and the error changed. I then had to update the

Re: gcc 4.2 miscompilation with -O2 -fno-omit-frame-pointer on amd64

2011-12-08 Thread Piotr Nowak
We're working on PowerPC target using GCC 4.2.1 and FreeBSD 6.1. It seems like we have similar problem. In our case GCC sometimes very unfortunately optimize code with -fno-omit-frame-pointer. Example shown below covers file sys/powerc/booke/pmap.c and function pmap_kenter. If we disassemble

Re: [SOLVED]Re: 64bit build errors - use gcc46

2011-12-08 Thread Da Rock
On 12/08/11 19:58, Tom Evans wrote: On Thu, Dec 8, 2011 at 6:05 AM, Da Rock freebsd-hack...@herveybayaustralia.com.au wrote: Just to let the list know, I changed as - ./configure --as=/usr/local/bin/as. I still had the exact same error oddly enough. I then had to install gcc46; and the error

USB Texas Instruments CDCE modem not recognized by cdce

2011-12-08 Thread Lorenzo Cogotti
Dear all, I am new to this list and to FreeBSD in general, so first of all hi everyone and thank you for providing this awesome and rock solid OS. I have a CDC compliant (at least this is what the manufacturer claims) USB Modem, which doesn't get detected by cdce module. /var/log/messages

Re: USB Texas Instruments CDCE modem not recognized by cdce

2011-12-08 Thread Hans Petter Selasky
On Thursday 08 December 2011 14:09:47 Lorenzo Cogotti wrote: Dear all, I am new to this list and to FreeBSD in general, so first of all hi everyone and thank you for providing this awesome and rock solid OS. I have a CDC compliant (at least this is what the manufacturer claims) USB Modem,

Re: USB Texas Instruments CDCE modem not recognized by cdce

2011-12-08 Thread Lorenzo Cogotti
Il giorno gio, 08/12/2011 alle 15.39 +0100, Hans Petter Selasky ha scritto: Typically you need to select configuration 1 for dual RNDIS/CDCE devices to work. 1) Locate your device: usbconfig 2) Set config 1 usbconfig -d X.Y set_config 1 To permanently do this, you can set the

Re: USB Texas Instruments CDCE modem not recognized by cdce

2011-12-08 Thread Lorenzo Cogotti
Il giorno gio, 08/12/2011 alle 16.35 +0100, Lorenzo Cogotti ha scritto: I tried editing if_cdce.c adding to the static array mentioned in my first mail: {USB_VPI(USB_VENDOR_TI, 0x6060, 0)}, I tried to remove this edit and recompile the kernel module, the scary messages faded away,

Re: USB Texas Instruments CDCE modem not recognized by cdce

2011-12-08 Thread Hans Petter Selasky
On Thursday 08 December 2011 16:35:47 Lorenzo Cogotti wrote: Il giorno gio, 08/12/2011 alle 15.39 +0100, Hans Petter Selasky ha scritto: Typically you need to select configuration 1 for dual RNDIS/CDCE devices to work. 1) Locate your device: usbconfig 2) Set config 1

Re: USB Texas Instruments CDCE modem not recognized by cdce

2011-12-08 Thread Hans Petter Selasky
On Thursday 08 December 2011 16:54:40 Lorenzo Cogotti wrote: Eventually, should I send a patch to someone so that I am not the only one to benefit from your help? If you want this quirk permanently you could try to add an entry to: /sys/dev/usb/quirk/usb_quirk.c You should use the quirk:

Re: gcc 4.2 miscompilation with -O2 -fno-omit-frame-pointer on amd64

2011-12-08 Thread Nathan Whitehorn
On 12/08/11 03:01, Piotr Nowak wrote: We're working on PowerPC target using GCC 4.2.1 and FreeBSD 6.1. It seems like we have similar problem. In our case GCC sometimes very unfortunately optimize code with -fno-omit-frame-pointer. Example shown below covers file sys/powerc/booke/pmap.c and

Re: gcc 4.2 miscompilation with -O2 -fno-omit-frame-pointer on amd64

2011-12-08 Thread Alexander Kabaev
On Sat, 19 Nov 2011 12:01:50 +0200 Gleb Kurtsou gleb.kurt...@gmail.com wrote: Hi, I was lucky to write a bit of code which gcc 4.2 fails to compile correctly with -O2. Too keep long story short the code fails for gcc from base system and last gcc 4.2 snapshot from ports. It works with gcc