Talk:Qualcomm Hexagon

To add into article

qdsp4 was 3 stage pipelined; qdsp5 was 6 stage pipelined. cs.nyu.edu/~sc2618/aboutme.html any hexagon was proprietary before 2011, when qualcomm dsp access program was started. Early versions was programmed in assembler only. developer.qualcomm.com/sites/default/files/qualcomm-dsp-access-program.pdf `a5b (talk) 01:24, 31 May 2012 (UTC)

Taylor Simpson, the manager in charge of the Linux port to Hexagon, gave a good talk about the Hexagon LLVM port in 2011, with lots of architectural tidbits: https://www.youtube.com/watch?v=MefebRh34cI — Preceding unsigned comment added by 172.58.139.149 (talk) 05:17, 14 November 2018 (UTC)

... and what is it good for?

Additionally to mentioning support by LLVM/Clang and by an out-of-tree GCC, it would be nice to at least mention, maybe even explain some of the use cases. The Hisilicon#KIRIN 920 SoC e.g. is said to contain an Image processor, usually being some specialized DSP. Can the Hexagon be used for image processing? Is it? AFAIK Nvidia claim to use their GPU SIMD stuff for a couple of things other the graphics processing. What about that? User:ScotXW^t@lk 18:19, 13 June 2014 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 3 external links on Qualcomm Hexagon. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive http://web.archive.org/web/20131224103934/https://rpw.io/slides/rpw-pacsec2013-hexagon.pdf to https://rpw.io/slides/rpw-pacsec2013-hexagon.pdf
• Added archive http://web.archive.org/web/20130528013532/http://www.fwdconcepts.com:80/dsp111212.htm to http://www.fwdconcepts.com/dsp111212.htm
• Added {{dead link}} tag to http://www.eetasia.com/articleLogin.do?artId=8800667242
• Added {{dead link}} tag to https://developer.qualcomm.com/download/80-nb419-3ahexagonvirtualmachinespec.pdf
• Added archive http://web.archive.org/web/20150114212717/https://developer.qualcomm.com/sites/default/files/qualcomm-dsp-access-program.pdf to https://developer.qualcomm.com/sites/default/files/qualcomm-dsp-access-program.pdf

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 12:22, 21 July 2016 (UTC)

The persistent URL you're looking for in citation 5 is probably http://landley.net/notes-2012.html#24-02-2012 — Preceding unsigned comment added by 172.58.99.237 (talk) 17:41, 18 May 2017 (UTC)

Too much explanation

A lot of this article describes things that are described in other pages. For example, there is no need to describe what exactly an instruction set or microarchitecture is when there are already great articles on these topics specifically. I'd like to clean up this article soon but the organization might have to change with so much information getting removed. RealSwiftCoderJoe (talk) 02:01, 2 March 2023 (UTC)