| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [Safestack] Fix the canary test to catch the libc's message regarding stack ↵ | Ivan A. Kosarev | 2017-05-10 | 1 | -1/+2 |
| | | | | | | | | | | | | | | | smashing By default glibc writes its diagnostics directly to tty so the `2>&1 |` redirection in the test doesn't catch the *** stack smashing detected *** message, which in turn breaks printing the lit's progress bar. By defining the LIBC_FATAL_STDERR_ environment variable we force glibc to direct diagnostic messages to stderr. Differential Revision: https://reviews.llvm.org/D32599 llvm-svn: 302628 | ||||
| * | [safestack] Fix stack canary test on Mac. | Evgeniy Stepanov | 2016-04-12 | 1 | -2/+2 |
| | | | | | | | | Disable FORTIFY_SOURCE and explicitly disable stack protector in the no-stack-protector run. llvm-svn: 266106 | ||||
| * | [safestack] A test for stackprotector canaries. | Evgeniy Stepanov | 2016-04-11 | 1 | -0/+37 |
| llvm-svn: 266006 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|