re: port-amd64/50989: Some programs in base dump dores with SIGILL

[christos%zoulas.com@localhost (Christos Zoulas)]

On Mar 22,  4:19am, mrg%eterna.com.au@localhost (matthew green) wrote:
-- Subject: re: port-amd64/50989: Some programs in base dump dores with SIGIL

| Christos, why do you think that your change to openssl isn't the real
| problem here?  now GCC 4.8 is getting its stack unaligned.
| 
| please revert your commits as listed in this PR:
| 
| > https://mail-index.netbsd.org/source-changes/2016/03/20/msg073540.html
| > https://mail-index.netbsd.org/source-changes/2016/03/20/msg073539.html
| > https://mail-index.netbsd.org/source-changes/2016/03/20/msg073538.html
| > https://mail-index.netbsd.org/source-changes/2016/03/20/msg073537.html
| > https://mail-index.netbsd.org/source-changes/2016/03/20/msg073536.html
| > 
| > After these commits, ssh, sshd, syslogd, ssh-agent, and some other programs
| > dump core with SIGILL illegal instruction.
| > 
| > My GCCl is 4.8.5.
| 
| 
| i have not seen any problem with GCC 5.3.  i'm happily running X11 with
| a bunch of GL and ssh on my amd4 box with a fully GCC 5.3 compiled by
| a GCC 5.3 world (though my pkgsrc build failed at around 690 packages
| i haven't looked at why yet -- though those were a 5.3 world that was
| compiled by 4.8.)
| 

This is SIGILL not SIGSEGV (which you get with an unaligned stack) which
means that the processor detection code is now incompatible with the
old assembly stubs. Which means in turn that I will either have to replace
all of it, or import a newer openssl. I'd rather do the latter one since
it is a waste of time to fix bugs already found and fixed.

christos