Announcement

Collapse
No announcement yet.

RadeonSI & Intel Both Get Patches For Boosting Compute Shader Performance

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

  • RadeonSI & Intel Both Get Patches For Boosting Compute Shader Performance

    Phoronix: RadeonSI & Intel Both Get Patches For Boosting Compute Shader Performance

    Both the Intel i965 and AMD RadeonSI drivers within Mesa have seen separate work done over the past day for boosting the performance of compute shaders with these open-source OpenGL drivers...

    http://www.phoronix.com/scan.php?pag...Compute-Shader

  • #2
    Originally posted by phoronix View Post
    Phoronix: RadeonSI & Intel Both Get Patches For Boosting Compute Shader Performance

    Both the Intel i965 and AMD RadeonSI drivers within Mesa have seen separate work done over the past day for boosting the performance of compute shaders with these open-source OpenGL drivers...

    http://www.phoronix.com/scan.php?pag...Compute-Shader
    Typo in the article: fastr

    Suggestion: Try a spell checker before the article is published, maybe "aspell -c file" or "aspell -a".
    Last edited by atomsymbol; 06-13-2016, 02:47 PM.

    Comment


    • #3
      Originally posted by phoronix View Post
      Phoronix: RadeonSI & Intel Both Get Patches For Boosting Compute Shader Performance

      Both the Intel i965 and AMD RadeonSI drivers within Mesa have seen separate work done over the past day for boosting the performance of compute shaders with these open-source OpenGL drivers...

      http://www.phoronix.com/scan.php?pag...Compute-Shader
      It appears that the "particular compute shader" is in Bioshock Infinite. Previously, Ultra and Very High settings were a slideshow.

      $ foo ./bioshock |& grep swizzle
      swizzle
      swizzle
      swizzle

      Comment


      • #4
        Originally posted by atomsymbol View Post

        Typo in the article: fastr

        Suggestion: Try to use a spell checker before the article is published, maybe "aspell -c file" or "aspell -a".
        Yeah... did you actually try doing that yourself? This is a relatively short article and there are 15 instances of "misspellings", not including "fastr". This is a tech site. Every other word will be considered misspelled. Considering the diversity of software and hardware that is written about here, there's no realistic way to build up a dictionary of these terms either. If Michael did a complete spell check for every article, he would end up with more mistakes, because of accidentally making corrections that weren't wrong. A typo now and then is inevitable for a website like this. It's actually impressive how few he creates.

        Comment


        • #5
          Originally posted by schmidtbag View Post
          Yeah... did you actually try doing that yourself? This is a relatively short article and there are 15 instances of "misspellings", not including "fastr". This is a tech site. Every other word will be considered misspelled. Considering the diversity of software and hardware that is written about here, there's no realistic way to build up a dictionary of these terms either. If Michael did a complete spell check for every article, he would end up with more mistakes, because of accidentally making corrections that weren't wrong. A typo now and then is inevitable for a website like this. It's actually impressive how few he creates.
          ? ? ?

          Comment


          • #6
            His browser should simply underline errors in red, that would be enough to prevent the vast majority of typos.
            ## VGA ##
            AMD: X1950XTX, HD3870, HD5870
            Intel: GMA45, HD3000 (Core i5 2500K)

            Comment


            • #7
              Originally posted by darkbasic View Post
              His browser should simply underline errors in red, that would be enough to prevent the vast majority of typos.
              Agreed, but you could eventually "tune-out" the red underlines after seeing them all day.

              Comment


              • #8
                Originally posted by schmidtbag View Post
                Yeah... did you actually try doing that yourself? This is a relatively short article and there are 15 instances of "misspellings", not including "fastr". This is a tech site. Every other word will be considered misspelled. Considering the diversity of software and hardware that is written about here, there's no realistic way to build up a dictionary of these terms either. If Michael did a complete spell check for every article, he would end up with more mistakes, because of accidentally making corrections that weren't wrong. A typo now and then is inevitable for a website like this. It's actually impressive how few he creates.
                It's called "proofreading", it's done by humans without any help from machines. It usually works unless you are in a grave hurry, typing from a mobile device, or both.

                Comment


                • #9
                  Originally posted by starshipeleven View Post
                  It usually works unless you are in a grave hurry, typing from a mobile device, or both.
                  Or, as any writer will tell you: reading your own work. No matter how much you fight it, your brain is still going to silently 'fix' mistakes as you read through it.

                  Comment


                  • #10
                    Originally posted by Ericg View Post
                    Or, as any writer will tell you: reading your own work. No matter how much you fight it, your brain is still going to silently 'fix' mistakes as you read through it.
                    Aw come on. We are not talking of Tolstoj-size books with an engaging story you can lose yourself in, but of short articles of cold, technical matters with numbers.

                    Anyway, "proofreader" used to be a profession back then, nowadays they are probably not employed anymore anywhere, if the low-quality writing I see everywhere is any indication (online and physical newspapers, blogs, and such).

                    The sad thing is that it's usually stuff that average machine-based autocorrection would have detected and solved automatically.

                    Comment

                    Working...
                    X