[all-commits] [llvm/llvm-project] 437a67: clang-offload-bundler: Remove conflicting-target-I...

Matt Arsenault via All-commits all-commits at lists.llvm.org
Wed Jul 15 05:34:27 PDT 2026


  Branch: refs/heads/users/arsenm/clang/offload-bundler-remove-conflict-targetid-diagnostic
  Home:   https://github.com/llvm/llvm-project
  Commit: 437a679908a92000fff1ed05d1c0d8c615c28f4e
      https://github.com/llvm/llvm-project/commit/437a679908a92000fff1ed05d1c0d8c615c28f4e
  Author: Matt Arsenault <Matthew.Arsenault at amd.com>
  Date:   2026-07-15 (Wed, 15 Jul 2026)

  Changed paths:
    M clang/docs/ClangOffloadBundler.rst
    M clang/include/clang/Driver/OffloadBundler.h
    M clang/lib/Driver/OffloadBundler.cpp
    M clang/test/OffloadTools/clang-offload-bundler/basic.c
    M clang/tools/clang-offload-bundler/ClangOffloadBundler.cpp

  Log Message:
  -----------
  clang-offload-bundler: Remove conflicting-target-ID diagnostic

This was checking that you did not try to combine arches with
any mode vs. a specific mode (e.g, gfx90a and gfx90a:xnack+). I
don't see any point in this diagnostic. All the modes have a natural
interpretation as distinct targets with a selection preference. It's
more defensible to have this rule in the user facing clang driver,
but not the low level binary utilities. This reduces the surface area
of some special case target ID parsing.

Co-authored-by: Claude (Opus 4.8)



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list