10
\$\begingroup\$

I recently asked a question that is at least in part specific to gcc. That is, the way the C code is written will be different for different compilers. This is because different compilers are able to vectorize different code.

Should there be a gcc tag so that people with the appropriate gcc specific expertise will know to look at it?

\$\endgroup\$
6
\$\begingroup\$

It sounds like a tag that some people might reasonably want to search/filter for, so I think it should be created.

\$\endgroup\$
7
\$\begingroup\$

To be honest, you would probably be better off asking that question on Stack Overflow. The question contains a short code snippet (which could be considered an MCVE), and you are asking a specific question about that code (how to get GCC to vectorize it) rather than for an open-ended critique.

That probably explains why no tag has been created on Code Review prior to this — it's too specific. And I see that you have asked a similar question on Stack Overflow before, with [gcc] and [auto-vectorization] tags.

\$\endgroup\$
  • \$\begingroup\$ You could be right but I am also asking for any advice about the code which people might have. \$\endgroup\$ – Lembik Jan 16 '17 at 18:43
  • \$\begingroup\$ I would still be in favor of removing it (I only added status-completed since it was already created). \$\endgroup\$ – Jamal Jan 17 '17 at 0:03
  • \$\begingroup\$ I agree, if only because the audience you'd be hoping to target with this question is more active on Stack Overflow. I'd like to see Code Review grow to handle low-level performance optimization questions (on working code, of course), but as things stand right now, I think Stack Overflow is one's best shot at a good answer. \$\endgroup\$ – Cody Gray Jan 17 '17 at 10:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .