Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1299599 - [gcc] Compilations fails with 'expected unqualified-id before token' when code contains vector class and macro and local var sharing same name
Summary: [gcc] Compilations fails with 'expected unqualified-id before token' when cod...
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 24
Hardware: ppc64le
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: PPCTracker F-ExcludeArch-ppc64le, PPC64LETracker
TreeView+ depends on / blocked
Reported: 2016-01-18 17:44 UTC by Rafael Fonseca
Modified: 2017-08-08 12:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-08-08 12:40:34 UTC

Attachments (Terms of Use)
gcc/ppc64le error reproducer (deleted)
2016-01-18 17:44 UTC, Rafael Fonseca
no flags Details

System ID Priority Status Summary Last Updated
GNU Compiler Collection 70296 None None None 2016-03-18 14:38:54 UTC

Description Rafael Fonseca 2016-01-18 17:44:16 UTC
Created attachment 1115927 [details]
gcc/ppc64le error reproducer

Description of problem: qucs fails to build on ppc64le [1]. The reason seems to be that during preprocessing, gcc strips out the variable name. And that seems to happen because there is a local variable of the type 'vector' named the same as a macro.

The attached test case reproduces the issue.


Version-Release number of selected component (if applicable): 5.3.1-2

How reproducible: always when building qucs on ppc64le-koji. Always when compiling attached code on ppc64le.

Steps to Reproduce:
1. g++ test.cpp

Actual results: test.cpp:59:11: error: expected unqualified-id before ‘=’ token
  vector R = sqrt(C * C) + test(C);

In the processed file:

main(int argc, char *argv[])
 int C = -1;
 vector = sqrt(C * C) + test(C);

 cout << C << " " << R << endl;

 return 0;

Expected results: compilation is successful (like in other arches).

Additional info: happens on f22, f23 and rawhide.

Comment 1 Jan Kurik 2016-02-24 14:18:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:

Comment 2 Martin Sebor 2016-03-16 19:34:42 UTC
The test case doesn't look quite right (there's no insertion operator matching std::ostream and ::vector) and doesn't compile even on x86_64.

There is a known problem with the name vector in the powerpc GCC, however:  That coule be behind the qucs build issue.

Comment 3 Jakub Jelinek 2016-03-18 14:38:55 UTC
Tracking upstream now in PR70296.

Comment 4 Fedora End Of Life 2017-07-25 19:48:05 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-08-08 12:40:34 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.