Re: Firefox 13
core2 != native maybe. Later Intel Core 2 (45nm) added SSE4.1. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Firefox-13-tp5716220p5716642.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On Fri, 8 Jun 2012, Olivier Smedts wrote: 2012/6/7 Warren Block : On Thu, 7 Jun 2012, Niclas Zeising wrote: On 2012-06-07 17:47, Warren Block wrote: Yesterday, Firefox 13 built and installed quickly. It was just the running part that did not go so well. Coredumps on start, it would start with add-ons disabled, but then coredump while typing a URL, or sometimes a few seconds later. Rebuilding everything Firefox depends on did not make any difference. Firefox 12 builds and runs fine, as do Chromium and xxxterm. This is on 9-stable from yesterday, amd64. The next step is to build with debug symbols; I was hoping the problem would have been experienced by someone else by now. Any ideas? Which compiler did you use, clang or gcc, and if gcc, which version? Regards! gcc46, and I do have CPUTYPE?=native in make.conf... Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug? /usr/share/mk/bsd.cpu.mk doesn't support CPUTYPE?=native : % make -VMACHINE_CPU CPUTYPE=native unknown amd64 sse2 sse mmx % make -VMACHINE_CPU CPUTYPE=core2 ssse3 sse3 amd64 sse2 sse mmx But you can use a supported value, add -march=native to your CFLAGS and COPTFLAGS, and set NO_CPU_CFLAGS=yes and NO_CPU_COPTFLAGS=yes so that another -march won't be automatically added. And if you use the old base-system gcc, -march=native won't give proper results with a Core2 and a Corei7 (not tested other recent CPUs) because they'll use -mtune=generic instead of the good -mtune. I prefer setting a proper -march. I don't know if thta's related to your firefox problem though. With CPUTYPE?=core2, Firefox 13 works fine. That "native" setting has been in my make.conf for a long time, but this is the first time it ever caused a problem.___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
2012/6/7 Warren Block : > On Thu, 7 Jun 2012, Niclas Zeising wrote: > >> On 2012-06-07 17:47, Warren Block wrote: >>> >>> Yesterday, Firefox 13 built and installed quickly. It was just the >>> running part that did not go so well. Coredumps on start, it would >>> start with add-ons disabled, but then coredump while typing a URL, or >>> sometimes a few seconds later. Rebuilding everything Firefox depends on >>> did not make any difference. >>> >>> Firefox 12 builds and runs fine, as do Chromium and xxxterm. >>> >>> This is on 9-stable from yesterday, amd64. The next step is to build >>> with debug symbols; I was hoping the problem would have been experienced >>> by someone else by now. Any ideas? >> >> >> Which compiler did you use, clang or gcc, and if gcc, which version? >> Regards! > > > gcc46, and I do have CPUTYPE?=native in make.conf... > > Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug? /usr/share/mk/bsd.cpu.mk doesn't support CPUTYPE?=native : % make -VMACHINE_CPU CPUTYPE=native unknown amd64 sse2 sse mmx % make -VMACHINE_CPU CPUTYPE=core2 ssse3 sse3 amd64 sse2 sse mmx But you can use a supported value, add -march=native to your CFLAGS and COPTFLAGS, and set NO_CPU_CFLAGS=yes and NO_CPU_COPTFLAGS=yes so that another -march won't be automatically added. And if you use the old base-system gcc, -march=native won't give proper results with a Core2 and a Corei7 (not tested other recent CPUs) because they'll use -mtune=generic instead of the good -mtune. I prefer setting a proper -march. I don't know if thta's related to your firefox problem though. Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On 7-6-2012 23:25, Warren Block wrote: > On Thu, 7 Jun 2012, Mel Flynn wrote: > >> On 7-6-2012 21:55, Warren Block wrote: >> >>> gcc46, and I do have CPUTYPE?=native in make.conf... >>> >>> Interesting! Built without CPUTYPE set, Firefox seems fine. >>> Compiler bug? >> >> Shot in the dark: SSE support? Based on threads earlier on this list >> with respect to chrome. > > SSE support by gcc, you mean? No idea, but just to make sure I rebuilt > with CPUTYPE?=native again, and that's definitely the problem. I was referring to this post: http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/075290.html While it's related to clang, CPUTYPE seems to have an effect on selected extensions and perhaps the root cause is there. Like I said, shot in the dark. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On Thu, 7 Jun 2012, Mel Flynn wrote: On 7-6-2012 21:55, Warren Block wrote: gcc46, and I do have CPUTYPE?=native in make.conf... Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug? Shot in the dark: SSE support? Based on threads earlier on this list with respect to chrome. SSE support by gcc, you mean? No idea, but just to make sure I rebuilt with CPUTYPE?=native again, and that's definitely the problem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On 7-6-2012 21:55, Warren Block wrote: > gcc46, and I do have CPUTYPE?=native in make.conf... > > Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug? Shot in the dark: SSE support? Based on threads earlier on this list with respect to chrome. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
Niclas Zeising writes: > Which compiler did you use, clang or gcc, and if gcc, which version? On: FreeBSD 10.0-CURRENT #0: Sun Mar 11 08:20:02 EDT 2012 amd64 and using clang, FireFox 13 builds and starts, but freezes after 2-3 seconds. The freeze locks focus (and therefore the mosue) on that window; it is possible to kill the process from the console using "kill -KILL". The only option set is "emable additional log messages". make.conf is available on request. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On Thu, Jun 7, 2012 at 2:55 PM, Warren Block wrote: > On Thu, 7 Jun 2012, Niclas Zeising wrote: > >> On 2012-06-07 17:47, Warren Block wrote: >>> >>> Yesterday, Firefox 13 built and installed quickly. It was just the >>> running part that did not go so well. Coredumps on start, it would >>> start with add-ons disabled, but then coredump while typing a URL, or >>> sometimes a few seconds later. Rebuilding everything Firefox depends on >>> did not make any difference. >>> >>> Firefox 12 builds and runs fine, as do Chromium and xxxterm. >>> >>> This is on 9-stable from yesterday, amd64. The next step is to build >>> with debug symbols; I was hoping the problem would have been experienced >>> by someone else by now. Any ideas? >> >> >> Which compiler did you use, clang or gcc, and if gcc, which version? >> Regards! > > > gcc46, and I do have CPUTYPE?=native in make.conf... > > Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug? Not really surprised about that. I have stopped tweak the CPUTYPE several years ago when I discovered that the FreeBSD machines got very and very stable without tweak CPUTYPE. I don't even notice any of performance difference. Maybe I will if I look at the numbers. ;-) Cheers, Mezz -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On Thu, 7 Jun 2012, Niclas Zeising wrote: On 2012-06-07 17:47, Warren Block wrote: Yesterday, Firefox 13 built and installed quickly. It was just the running part that did not go so well. Coredumps on start, it would start with add-ons disabled, but then coredump while typing a URL, or sometimes a few seconds later. Rebuilding everything Firefox depends on did not make any difference. Firefox 12 builds and runs fine, as do Chromium and xxxterm. This is on 9-stable from yesterday, amd64. The next step is to build with debug symbols; I was hoping the problem would have been experienced by someone else by now. Any ideas? Which compiler did you use, clang or gcc, and if gcc, which version? Regards! gcc46, and I do have CPUTYPE?=native in make.conf... Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Firefox 13
On 2012-06-07 17:47, Warren Block wrote: > Yesterday, Firefox 13 built and installed quickly. It was just the > running part that did not go so well. Coredumps on start, it would > start with add-ons disabled, but then coredump while typing a URL, or > sometimes a few seconds later. Rebuilding everything Firefox depends on > did not make any difference. > > Firefox 12 builds and runs fine, as do Chromium and xxxterm. > > This is on 9-stable from yesterday, amd64. The next step is to build > with debug symbols; I was hoping the problem would have been experienced > by someone else by now. Any ideas? Which compiler did you use, clang or gcc, and if gcc, which version? Regards! -- Niclas ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Firefox 13
Yesterday, Firefox 13 built and installed quickly. It was just the running part that did not go so well. Coredumps on start, it would start with add-ons disabled, but then coredump while typing a URL, or sometimes a few seconds later. Rebuilding everything Firefox depends on did not make any difference. Firefox 12 builds and runs fine, as do Chromium and xxxterm. This is on 9-stable from yesterday, amd64. The next step is to build with debug symbols; I was hoping the problem would have been experienced by someone else by now. Any ideas? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
