Announcement

Collapse
No announcement yet.

GCC 11 Picks Up A New Option For Large Source Files

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GCC 11 Picks Up A New Option For Large Source Files

    Phoronix: GCC 11 Picks Up A New Option For Large Source Files

    When seeing GCC 11 in its early development state pick up a new -flarge-source-files option I was curious what that was all about......

    http://www.phoronix.com/scan.php?pag...e-source-files

  • #2
    if just someone invited dynamically sized buffers, ..! 🤔

    Comment


    • #3
      Makes no sense. There are industry guidelines for producing good code. Functions and modules should be split when they exceed certain threshold, e.g. screen size.

      Comment


      • #4
        Originally posted by caligula View Post
        Makes no sense. There are industry guidelines for producing good code. Functions and modules should be split when they exceed certain threshold, e.g. screen size.
        You're gonna be really pissed when Linus upgrades to a 72" screen.

        Comment


        • #5
          Originally posted by caligula View Post
          Makes no sense. There are industry guidelines for producing good code. Functions and modules should be split when they exceed certain threshold, e.g. screen size.
          Amalgamation builds are still a thing. So are generated source files.

          There always has to be at least one know-it-all who says "b-but muh industry guidelines".

          Comment


          • #6
            Originally posted by caligula View Post
            Makes no sense. There are industry guidelines for producing good code. Functions and modules should be split when they exceed certain threshold, e.g. screen size.
            Are there really people splitting modules based on screen size?
            That seems a very arbitrary way to make things more illogical.

            Comment


            • #7
              This is for when converting assets into source files, not for actual hand written code.

              Comment


              • #8
                Originally posted by caligula View Post
                Makes no sense.
                There is a lot of existing code out there for which no company (or individual) is willing/able to refactor into smaller units, for various reasons (constructed code, code which has passed various (expensive) validations, etc.). It is all well and good to talk about the theory of how one should write good/maintainable code, but in the real (practical) world that is not the way the code sometimes is, and providing additional diagnostic capability in your compiler is a good thing.

                Comment


                • #9
                  Originally posted by remenic View Post
                  This is for when converting assets into source files, not for actual hand written code.
                  This sounds like something the linker (scripts) should do. It makes little sense to translate binary into some hex array, then back to binary.

                  Comment


                  • #10
                    Originally posted by caligula View Post
                    This sounds like something the linker (scripts) should do. It makes little sense to translate binary into some hex array, then back to binary.
                    It makes plenty of sense if you want it to be portable.

                    Comment

                    Working...
                    X