On Mon, Jan 12, 2015 at 10:50:07PM +0100, Till Maas wrote: > On Mon, Jan 12, 2015 at 03:37:42PM -0500, Miloslav Trmač wrote: > > ----- Original Message ----- > > > Does this proposal apply to native non-C/C++ programs? > > > > As written, it seems to intend so. In practice, it would probably > > apply or not depending on whether the non-C/C++ programs’ builds are > > affected by _hardened_build. > > I did not think of these programs, so I agree here. Addressing them is > something for a future change proposal IMHO, unless there is enough time > to to do for F22. > > > Ideally, I think this should apply to all languages that don’t ensure > > memory safety, and not to those that do ensure it.¹ (There is also > > the edge case of safe languages with explicit “unsafe” blocks, I guess > > these should default into the “safe” category?) Mirek > > Is there a list of languages that need to be considered? There is afaik > golang, ocaml and ghc that need to be considered. Probably Ada (ie. gnat), Fortran (gfortran), ObjC. Are there any other gcc frontends? LDC (D) can generate native binaries too. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
