Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A asdf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • asdf
  • asdf
  • Issues
  • #107

Closed
Open
Created Jan 27, 2022 by Eric Timmons@etimmonsOwner

ABCL expands compiler macros overeagerly

Sometimes ASDF/UIOP calls its own deprecated functions. We typically prevent these calls from producing warnings by declaring calls to deprecated functions as notinline. According to 3.2.2.1.3 this must prevent compiler macro expansion.

However, ABCL still expands the compiler macros in generic functions, potentially resulting in warnings when compiling ASDF.

I noticed when prepping for ASDF 3.4. Reported at https://abcl.org/trac/ticket/487. I figured this is worth tracking, so I'm making a new issue category for implementation-bug

Assignee
Assign to
Time tracking