Date: Thu, 16 Nov 2006 21:56:39 -0500 From: Alexander Kabaev <kabaev@gmail.com> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Andriy Gapon <avg@icyb.net.ua> Subject: Re: ZFS patches for FreeBSD. Message-ID: <20061116215639.73d00824@kan.dnsalias.net> In-Reply-To: <200611161506.58128.jkim@FreeBSD.org> References: <1163701391.00638085.1163691003@10.7.7.3> <455CB8CA.8040603@icyb.net.ua> <200611161506.58128.jkim@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Thu, 16 Nov 2006 15:06:56 -0500
Jung-uk Kim <jkim@FreeBSD.org> wrote:
> On Thursday 16 November 2006 02:15 pm, Andriy Gapon wrote:
> > Hmm, I saw errors like this with some other 3rd party kernel module
> > when its sources had constructs like:
> >
> > struct some_struct s = {0};
> >
> > Changing the above initialization to explicit bzero() call helped
> > in that case, but I think that there should be some compiler flags
> > or something to handle this.
>
> AFAIK, there was no way to handle this GCC bug with compiler flags.
> '-ffreestanding' should prevent this to happen but it does not. As
> Max Laier pointed out, it was discussed long time ago. Bruce Evans
> had good analysis on this issue, too.
>
> Jung-uk Kim
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe@freebsd.org"
This is not a GCC bug. -ffreestanding is _documented_ as requiring
memset and friends as resolvable extern symbols. We were just lucky to
get away without it before.
--
Alexander Kabaev
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFFXSTqQ6z1jMm+XZYRAsjxAKCSietsAqGiPX6N3SQOBlHy3fuLXACg52MT
DLASmMhgEraxIEFNxiNU9wI=
=rzgl
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061116215639.73d00824>