RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1273484 - CentOS7 problem with gcc
Summary: CentOS7 problem with gcc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gcc
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jakub Jelinek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-20 14:25 UTC by Daniel U. Thibault
Modified: 2015-10-21 08:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-21 08:18:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Daniel U. Thibault 2015-10-20 14:25:59 UTC 
Description of problem:

Unexpected gcc error during compilation of LTTng 2.7.0-stable lttng-modules (1f7d83a) on CentOS Linux release 7.1.1503 (Core) (64 bits), running kernel 3.10.0-229.7.2.el7

  CC [M]  /usr/src/lttng-modules-2.7.0-stable/lttng-syscalls.o
/usr/src/kernels/3.10.0-229.el7.x86_64/arch/x86/include/asm/current.h: Assembler messages:
/usr/src/kernels/3.10.0-229.el7.x86_64/arch/x86/include/asm/current.h:14: Warning: end of file not at end of a line; newline inserted
{standard input}:16215: Error: unknown pseudo-op: `.'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
gcc: internal compiler error: Killed (program cc1)

/usr/src/kernels/3.10.0-229.el7.x86_64/arch/x86/include/asm/current.h is NOT truncated

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

gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9)

How reproducible:

Very.

Steps to Reproduce:
1. Fetch http://git.lttng.org/?p=lttng-modules.git;a=snapshot;h=1f7d83a89fd4c975f0e3fccd55fa59e03527152e;sf=tgz (you may also need glib2-devel-2.40.0-4.el7, gtk2-devel-2.24.22-5.el7_0.1, ncurses-devel-5.9-13.20130511.el7, pango-devel-1.34.1-5.el7, popt-devel-1.13-16.el7, uuid-devel-1.6.2-26.el7)
2. Deploy the tar.gz to e.g. /usr/src/
3. From the deployment folder, run $ make &> make.log

Actual results:

The error quoted above.

Expected results:

Should compile.

Additional info:

I've compiled the same lttng-modules package on Ubuntu 12.04.5 without any issue (gcc Ubuntu/Linaro 4.6.3-1ubuntu5, kernel 3.9.3).
Comment 1 Marek Polacek 2015-10-20 14:28:48 UTC 
This almost always means that the machine doesn't have enough memory and the OOM killer kills the cc1 process.
Comment 3 Daniel U. Thibault 2015-10-20 20:47:00 UTC 
Indeed, increasing the virtual machine's memory solved the problem.

So I guess teh bug should be relabelled something like 'gcc should report out-of-memory errors in a more obvious way'. Because that error message was pretty well obfuscated.
Comment 4 Marek Polacek 2015-10-21 08:18:01 UTC 
There's an upstream PR for this now:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68038

I think we can close this bug now; please reopen if you have any further questions.
Note You need to log in before you can comment on or make changes to this bug.