https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
Martin Uecker changed:
What|Removed |Added
CC||muecker at gwdg dot de
--- Comment #7 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #6 from qinzhao at gcc dot gnu.org ---
(In reply to Joseph S. Myers from comment #5)
> It's doubtful that this is a bug. You could define __builtin_choose_expr so
> the unselected operand only needs to be a balanced token sequence (wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #5 from Joseph S. Myers ---
It's doubtful that this is a bug. You could define __builtin_choose_expr so the
unselected operand only needs to be a balanced token sequence (with no commas
unless nested inside () [] {}), but it's less cl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Severity|minor |normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #4 from qinzhao at gcc dot gnu.org ---
the adoption of the new builtin __builtin_get_counted_by (PR116016) depends on
fixing this PR.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #3 from joseph at codesourcery dot com 2010-10-18 19:55:25 UTC ---
On Mon, 18 Oct 2010, pinskia at gcc dot gnu.org wrote:
> checking on the two arguments. Not to mention __builtin_choose_expr was
> added
> only to support Altivec i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #2 from kevin.waugh at gmail dot com 2010-10-18 19:17:17 UTC ---
(In reply to comment #1)
> I think this is correct as __builtin_choose_expr still does semantically
> checking on the two arguments. Not to mention __builtin_choose_exp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46073
--- Comment #1 from Andrew Pinski 2010-10-18
19:00:51 UTC ---
I think this is correct as __builtin_choose_expr still does semantically
checking on the two arguments. Not to mention __builtin_choose_expr was added
only to support Altivec intrin
