Date: Sun, 07 Feb 2016 19:15:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206990] powerpc (32-bit), projects/clang380-import vs. 11.0-CURRENT's sendsig: need to avoid signal delivery trashing the stack and so causing SIGSEGV Message-ID: <bug-206990-8-m7THLgCAbY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206990-8@https.bugs.freebsd.org/bugzilla/> References: <bug-206990-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206990 --- Comment #4 from Mark Millard <markmi@dsl-only.net> --- (In reply to Nathan Whitehorn from comment #2) If I'm going to submit a defect to the llvm folks I'd like to be able to accurately identify the proper ABI document and what section(s) of material that the 3.8.0 generated code violates. Otherwise my report is just hear-sa= y. What is the official PowerpC (32-bit) ELF ABI document that FreeBSD is base= d on and expects clang 3.8.0 to adhere to for the clang compiler options that buildworld uses? SunSoft's 1995-Sept "System V Application Binary Interface PowerPC Processor Supplement"? Something else? (Hopefully I can get a copy.) I should be able to say something like. . . Clang 3.8.0's "Target: powerpc-unknown-freebsd11.0" handling is supposed to= be based on ??? and so should handle the stack pointer per section(s) ??? in t= hat document. Instead it is generating code that looks like: . . . which would require a "red zone" like for 32-bit PowerPC Darwin's ABI or the 32-bit PowerPC AIX ABI. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206990-8-m7THLgCAbY>