Date: Wed, 24 Oct 2012 14:02:25 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Volodymyr Kostyrko <c.kworr@gmail.com> Cc: freebsd-stable@freebsd.org, Dimitry Andric <dim@freebsd.org> Subject: Re: wine, gcc and clang with CPUTYPE Message-ID: <20121024110225.GB35915@deviant.kiev.zoral.com.ua> In-Reply-To: <5087C428.2020908@gmail.com> References: <50879F62.2010004@gmail.com> <5087BD71.9090002@FreeBSD.org> <5087C428.2020908@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--/dCIfOYSJNmJ3drl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 24, 2012 at 01:34:16PM +0300, Volodymyr Kostyrko wrote: > 24.10.2012 13:05, Dimitry Andric wrote: > >> I just have taken some time to inspect CPUTYPE support for clang. It > >> seems to me that clang generates incorrect code in some cases. > >> > >> The first failure point I discovered was inability to build gcc from > >> sources or compile something with gcc. Code produced by gcc seem to fa= il > >> whether this was gcc compiled from bootstrap or anything else: > >> > >> http://lists.freebsd.org/pipermail/freebsd-multimedia/2012-October/013= 469.html > > > > Can you attempt to figure out what the illegal instruction was, in that > > case? >=20 > How can I do that? I'm not very familiar with gdb. Load the coredump in gdb, like gdb /path/to/the/binary binary.core then, at the gdb prompt, do info registers disassemble (if the later command emited an error, do disassemble x,x+10 where x is the content of the %eip register). Post the verbatim results of the whole gdb session. --/dCIfOYSJNmJ3drl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlCHysEACgkQC3+MBN1Mb4iSjwCfU3T2QEo1XeMVPuF1iYO/tsSQ 2lcAoIDxmkSOY2J17AJUBs7YKTvrqGok =0cvR -----END PGP SIGNATURE----- --/dCIfOYSJNmJ3drl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121024110225.GB35915>