Labels Milestones

New Issue

Tail call requirements should be discussed #100

Closed

opened 5 years ago by wschmidt-ibm · 0 comments

wschmidt-ibm commented 5 years ago (Migrated from github.com)

Neither ELFv1 nor ELFv2 ABIs discuss tail call optimization by compilers or assembly programmers. There are limitations on these that should be called out. For example, we recently discovered glibc was breaking the effective ABI by using assembly code to generate a tail call across compilation boundaries, something which is not allowed (since there is no way to know if the TOC is preserved, and no way to restore it upon return). The ABI should not be completely silent on this topic.

Neither ELFv1 nor ELFv2 ABIs discuss tail call optimization by compilers or assembly programmers. There are limitations on these that should be called out. For example, we recently discovered glibc was breaking the effective ABI by using assembly code to generate a tail call across compilation boundaries, something which is not allowed (since there is no way to know if the TOC is preserved, and no way to restore it upon return). The ABI should not be completely silent on this topic.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

v1.5

v1.5_markup

V1.4

1.2b

1.5_prd

Labels

Apply labels

Clear labels   

bug

  

duplicate

  

enhancement

  

help wanted

  

invalid

  

question

  

wontfix

No Label

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Set milestone

Clear milestone

No items

No Milestone

Projects

Set Project

Clear projects

No project

Assignees

Assign users

Clear assignees

No Assignees

1 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: systemsoftware/ELFv2-ABI#100

Write Preview

Loading…

Cancel

Save

There is no content yet.