Skip to content

Conversation

@shahmishal
Copy link
Member

On Windows and macOS, the filesystem is case insensitive, and these files
interfere with each other. Reading through, the case of the file extension
is part of the test. I've altered the rest of the name instead.

(cherry picked from commit 6c0a160)
(cherry picked from commit 0a1b111)

On Windows and macOS, the filesystem is case insensitive, and these files
interfere with each other. Reading through, the case of the file extension
is part of the test. I've altered the rest of the name instead.

(cherry picked from commit 6c0a160)
(cherry picked from commit 0a1b111)
@hyp
Copy link

hyp commented Oct 30, 2019

LGTM.

@shahmishal shahmishal merged commit 8c69892 into swiftlang:apple/stable/20190619 Oct 30, 2019
@shahmishal shahmishal deleted the fix-file-name-issue branch October 30, 2019 17:14
swift-ci pushed a commit that referenced this pull request Aug 25, 2025
llvm#137975)

An authenticated pointer can be explicitly checked by the compiler via a
sequence of instructions that executes BRK on failure. It is important
to recognize such BRK instruction as checking every register (as it is
expected to immediately trigger an abnormal program termination) to
prevent false positive reports about authentication oracles:

      autia   x2, x3
      autia   x0, x1
      ; neither x0 nor x2 are checked at this point
      eor     x16, x0, x0, lsl #1
      tbz     x16, #62, on_success ; marks x0 as checked
      ; end of BB: for x2 to be checked here, it must be checked in both
      ; successor basic blocks
    on_failure:
      brk     0xc470
    on_success:
      ; x2 is checked
      ldr     x1, [x2] ; marks x2 as checked
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants