Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. C1001: Internal compiler error
Forum Updated to NodeBB v4.3 + New Features

C1001: Internal compiler error

Scheduled Pinned Locked Moved Unsolved General and Desktop
6 Posts 3 Posters 762 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    knehez
    wrote on last edited by
    #1

    We are using qt 6.5.3 - Visual Studio 2022 17.9.6 in a huge desktop project.

    After upgrading VS 2022 to 17.10.4 the same project won't be compiled:

    ...... \qt_6_5_3\include\QtCore\qrect.h(621): fatal  error C1001: Internal compiler error.
    2>(compiler file 'D:\a\_work\1\s\src\vctools\Compiler\Utc\src\p2\main.c', line 242)
    

    Can anyone help me? (after downgrading VS 2022 back, it works again.)
    Have you ever experienced a similar or same problem?
    Thanks,
    Karoly

    JonBJ 1 Reply Last reply
    0
    • K knehez

      We are using qt 6.5.3 - Visual Studio 2022 17.9.6 in a huge desktop project.

      After upgrading VS 2022 to 17.10.4 the same project won't be compiled:

      ...... \qt_6_5_3\include\QtCore\qrect.h(621): fatal  error C1001: Internal compiler error.
      2>(compiler file 'D:\a\_work\1\s\src\vctools\Compiler\Utc\src\p2\main.c', line 242)
      

      Can anyone help me? (after downgrading VS 2022 back, it works again.)
      Have you ever experienced a similar or same problem?
      Thanks,
      Karoly

      JonBJ Offline
      JonBJ Offline
      JonB
      wrote on last edited by
      #2

      @knehez said in C1001: Internal compiler error:

      VS 2022 to 17.10.4

      Although I don't find your error for Qt on the web (you may be the first!?), Googling VS 2022 17.10.4 bugs C1001 comes across a few others?

      1 Reply Last reply
      0
      • Christian EhrlicherC Online
        Christian EhrlicherC Online
        Christian Ehrlicher
        Lifetime Qt Champion
        wrote on last edited by Christian Ehrlicher
        #3

        If cl.exe throws an ice then you should tell MS about it, Qt can't do anything about this (how should it).

        Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
        Visit the Qt Academy at https://academy.qt.io/catalog

        1 Reply Last reply
        0
        • K Offline
          K Offline
          knehez
          wrote on last edited by knehez
          #4

          First I tryed to google about this issue, I know it is a MS related problem, but I cannot create a small reproducible example project to show them. :-(
          Thanks for the help, I'll try to upgrade QT, maybe it helps.

          JonBJ 1 Reply Last reply
          0
          • K knehez

            First I tryed to google about this issue, I know it is a MS related problem, but I cannot create a small reproducible example project to show them. :-(
            Thanks for the help, I'll try to upgrade QT, maybe it helps.

            JonBJ Offline
            JonBJ Offline
            JonB
            wrote on last edited by
            #5

            @knehez
            You don't need a reproducer since other people are reporting same error on whatever other similar code they have. Per Google you may need to wait for a patch/upgrade to VS version, or downgrade. If you are lucky a different Qt version might not cause the same error, though wouldn't surprise me if it remains the same on same Qt code.

            What does surprise me is that the VS 2022 17.10.4 only got released on July 9th, so why would you move to it so quickly on "a huge desktop project"? If you have a huge project don't change compiler version when it's so new, else you're asking for trouble just like this....

            1 Reply Last reply
            1
            • K Offline
              K Offline
              knehez
              wrote on last edited by
              #6

              Yes, it was really a bad idea to use the "latest" build tools. I have moved back to (v14.39-17.9)
              image.png.

              1 Reply Last reply
              1

              • Login

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Users
              • Groups
              • Search
              • Get Qt Extensions
              • Unsolved