summaryrefslogtreecommitdiff
path: root/completions/gcc
blob: bafb81b73b27e75f7069705ee62b8e8960d9bdb4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
# gcc(1) completion                                        -*- shell-script -*-
#
# The only unusual feature is that we don't parse "gcc --help -v" output
# directly, because that would include the options of all the other backend
# tools (linker, assembler, preprocessor, etc) without any indication that
# you cannot feed such options to the gcc driver directly.  (For example, the
# linker takes a -z option, but you must type -Wl,-z for gcc.)  Instead, we
# ask the driver ("g++") for the name of the compiler ("cc1"), and parse the
# --help output of the compiler.

_gcc()
{
    local cur prev words cword
    _init_completion || return

    _expand || return 0

    local cc backend

    case $1 in
        gcj)
            backend=jc1
            ;;
        gpc)
            backend=gpc1
            ;;
        *77)
            backend=f771
            ;;
        *)
            backend=cc1 # (near-)universal backend
            ;;
    esac

    if [[ "$cur" == -* ]]; then
        cc=$( $1 -print-prog-name=$backend 2>/dev/null )
        [[ $cc ]] || return
        # sink stderr:
        # for C/C++/ObjectiveC it's useless
        # for FORTRAN/Java it's an error
        COMPREPLY=( $( compgen -W "$( $cc --help 2>/dev/null | \
           tr '\t' ' ' | \
           sed -e '/^  *-/!d' -e 's/ *-\([^ ]*\).*/-\1/' | \
           sort -u )" -- "$cur" ) )
    else
        _filedir
    fi
} &&
complete -F _gcc gcc g++ c++ g77 gcj gpc

[[ $OSTYPE == *cygwin* ]] || _userland GNU && _have gcc && \
    complete -F _gcc cc || :

# ex: ts=4 sw=4 et filetype=sh